Travel assistance service request - Revision history

Stefanseiler at 13:59, 26 January 2026

2026-01-26T13:59:53Z

← Older revision		Revision as of 13:59, 26 January 2026
Line 30:		Line 30:
	* [[TASR - Delivery partner perspective\|Delivery partner perspective]] - The delivery partners receive information from the OC when to delivery which service. They can accept/reject and request or provide more information on service delivery from the OC.		* [[TASR - Delivery partner perspective\|Delivery partner perspective]] - The delivery partners receive information from the OC when to delivery which service. They can accept/reject and request or provide more information on service delivery from the OC.

	You can read up this article on [[SARA data domains]] for further details.		You can read up this article on [[KORDEUS PAX - Data privacy analysis\|SARA data domains]] for further details.

	== Related articles ==		== Related articles ==
	* [[Kordeus.PAX]]		* [[Kordeus.PAX]]
	* [[~~SARA data domains~~]]		* [[KORDEUS PAX - Data privacy analysis]]
	__NOTOC__		__NOTOC__

Stefanseiler: /* Case standard process flow */

2025-06-26T08:58:28Z

Case standard process flow

← Older revision		Revision as of 08:58, 26 June 2025
Line 1:		Line 1:
	[[File:TAR standard management flow.png\|thumb\|standard assistance request flow\|634x634px]]A ''travel assistance service request'' holds all information of a '''partient requesting assistance''' on its upcoming journey. Once filed, the [[Travel assistance service operation center digitals\|travel assistance service operation centers]] in charge of requested segments will [[Dev:Travel Segment Service Item Claiming\|claim responsibility]] for service delivery on segments and will open a [[travel assistance service request case]], which is the leading data entity along the entire process flow from the request to service delivery.		[[File:TAR standard management flow.png\|thumb\|standard assistance request flow\|634x634px]]A ''travel assistance service request'' holds all information of a '''partient requesting assistance''' on its upcoming journey. Once filed, the [[Travel assistance service operation center digitals\|travel assistance service operation centers]] in charge of requested segments will [[Dev:Travel Segment Service Item Claiming\|claim responsibility]] for service delivery on segments and will open a travel assistance service request case, which is the leading data entity along the entire process flow from the request to service delivery.

	== Case standard process flow ==		== Case standard process flow ==
	=== Flowtype A: Regular request ===		=== Flowtype A: Regular request ===

	# '''Request creation phase''' - the PAX or the travel agent collects all information on his side on a travel assistance service request before submitting it. As third alternative, the operation center enters the request manually after receiving a request over an insecure channel, like email. At the end of this phase, there exists a valid [[travel assistance service request case]]		# '''Request creation phase''' - the PAX or the travel agent collects all information on his side on a travel assistance service request before submitting it. As third alternative, the operation center enters the request manually after receiving a request over an insecure channel, like email. At the end of this phase, there exists a valid travel assistance service request case
	# '''Decision preparation phase''' - the operation center and the passenger collaborate on reaching the point where the request can be confirmed		# '''Decision preparation phase''' - the operation center and the passenger collaborate on reaching the point where the request can be confirmed
	# '''Service delivery phase''' - the operation center coordinates the service delivery with its delivery partners		# '''Service delivery phase''' - the operation center coordinates the service delivery with its delivery partners

Stefanseiler at 07:13, 26 June 2025

2025-06-26T07:13:10Z

← Older revision		Revision as of 07:13, 26 June 2025
Line 33:		Line 33:

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

	* [[Kordeus.PAX]]		* [[Kordeus.PAX]]
	* [[SARA data domains]]		* [[SARA data domains]]
			__NOTOC__

Stefanseiler at 07:12, 26 June 2025

2025-06-26T07:12:53Z

← Older revision		Revision as of 07:12, 26 June 2025
Line 35:		Line 35:

	* [[Kordeus.PAX]]		* [[Kordeus.PAX]]
	* [[~~Travel assistance service request case~~]]		* [[SARA data domains]]

Stefanseiler: /* Data domains & Perspectives */

2025-06-26T07:10:08Z

Data domains & Perspectives

← Older revision		Revision as of 07:10, 26 June 2025
Line 25:		Line 25:
	A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. This results in different perspectives and tools for request processing:		A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. This results in different perspectives and tools for request processing:

	* [[TASR - Travel agent perspective\|Travel agent perspective]]		* [[TASR - Travel agent perspective\|Travel agent perspective]] - The travel agent only has proprietary information on grouping of his customers. The case handling acts on behalf of the passengers, so they have the patient's perspective once the enter a specific case
	* [[TASR - Passenger perspective\|Passenger perspective]]		* [[TASR - Passenger perspective\|Passenger perspective]] - The passenger has to provide the request and required information for getting the approval for its requests.
	* [[TASR - Operation center perspective\|Operation center perspective]]		* [[TASR - Operation center perspective\|Operation center perspective]] - The OC recieves information and has to come to the point of approval or rejection of the request. Once this point is received it has to govern the assistance service delivery process and needs to instruct and monitor the partners finally delivering the assistance services
	* [[TASR - Delivery partner perspective\|Delivery partner perspective]]		* [[TASR - Delivery partner perspective\|Delivery partner perspective]] - The delivery partners receive information from the OC when to delivery which service. They can accept/reject and request or provide more information on service delivery from the OC.

	You can read up this article on [[SARA data domains]] for further details.		You can read up this article on [[SARA data domains]] for further details.

Stefanseiler: /* Data domains & Perspectives */

2025-06-26T06:53:38Z

Data domains & Perspectives

← Older revision		Revision as of 06:53, 26 June 2025
Line 25:		Line 25:
	A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. This results in different perspectives and tools for request processing:		A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. This results in different perspectives and tools for request processing:

	* Travel agent perspective		* [[TASR - Travel agent perspective\|Travel agent perspective]]
	* Passenger perspective		* [[TASR - Passenger perspective\|Passenger perspective]]
	* Operation center perspective		* [[TASR - Operation center perspective\|Operation center perspective]]
	* Delivery partner perspective		* [[TASR - Delivery partner perspective\|Delivery partner perspective]]

	You can read up this article on [[SARA data domains]] for further details.		You can read up this article on [[SARA data domains]] for further details.

Stefanseiler: /* Data domains & Perspectives */

2025-06-26T06:52:14Z

Data domains & Perspectives

← Older revision		Revision as of 06:52, 26 June 2025
Line 23:		Line 23:
	* '''Transformation''' - the general inquiry can be change to a regular request, if the PAX adds a journey and booking during the inquiry process. In that moment, the decision the process will continue with the decision preparation phase of the regular request.		* '''Transformation''' - the general inquiry can be change to a regular request, if the PAX adds a journey and booking during the inquiry process. In that moment, the decision the process will continue with the decision preparation phase of the regular request.
	== Data domains & Perspectives ==		== Data domains & Perspectives ==
	A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. ~~See~~ this article on [[SARA data domains]] for further details.		A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. This results in different perspectives and tools for request processing:

			* Travel agent perspective
			* Passenger perspective
			* Operation center perspective
			* Delivery partner perspective

			You can read up this article on [[SARA data domains]] for further details.

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

Stefanseiler at 06:49, 26 June 2025

2025-06-26T06:49:04Z

← Older revision		Revision as of 06:49, 26 June 2025
Line 1:		Line 1:
	[[File:TAR standard management flow.png\|thumb\|standard assistance request flow\|634x634px]]A ''travel assistance service request'' ~~is created by a personal digital at a [[PAX.Portal]] instance~~ of a ~~carrier or agent~~. Once ~~is completed~~, ~~it is submitted to one or muliple~~ [[Travel assistance service operation center digitals\|operation centers]] ~~(e.g. LH MOC), which~~ [[Dev:Travel Segment Service Item Claiming\|claim responsibility]] for segments ~~they are responsible for handling special~~ assistance ~~requests~~.		[[File:TAR standard management flow.png\|thumb\|standard assistance request flow\|634x634px]]A ''travel assistance service request'' holds all information of a '''partient requesting assistance''' on its upcoming journey. Once filed, the [[Travel assistance service operation center digitals\|travel assistance service operation centers]] in charge of requested segments will [[Dev:Travel Segment Service Item Claiming\|claim responsibility]] for service delivery on segments and will open a [[travel assistance service request case]], which is the leading data entity along the entire process flow from the request to service delivery.

	== ~~Standard~~ process flow ==		== Case standard process flow ==
	=== Flowtype A: Regular request ===		=== Flowtype A: Regular request ===

Stefanseiler: /* Related articles */

2025-06-26T06:34:18Z

← Older revision		Revision as of 06:34, 26 June 2025
Line 4:		Line 4:
	=== Flowtype A: Regular request ===		=== Flowtype A: Regular request ===

	# '''Request creation phase''' - the PAX or the travel agent collects all information on his side on a travel assistance service request before submitting it. As alternative, the operation center enters the request manually, ~~if not received over PAX portal~~.		# '''Request creation phase''' - the PAX or the travel agent collects all information on his side on a travel assistance service request before submitting it. As third alternative, the operation center enters the request manually after receiving a request over an insecure channel, like email. At the end of this phase, there exists a valid [[travel assistance service request case]]
	# '''Decision preparation phase''' - the operation center and the passenger collaborate on reaching the point where the request can be confirmed		# '''Decision preparation phase''' - the operation center and the passenger collaborate on reaching the point where the request can be confirmed
	# '''Service delivery phase''' - the operation center coordinates the service delivery with its delivery partners		# '''Service delivery phase''' - the operation center coordinates the service delivery with its delivery partners
Line 16:		Line 16:
	=== Flowtype B: General inquiry ===		=== Flowtype B: General inquiry ===

	# '''Request creation phase''' (only on PAX portal) - the PAX or the travel agent collects all information on his side on a travel assistance service request before submitting it. As alternative, the operation center enters the request manually, if not received over PAX portal.		# '''Request creation phase'''
	# '''General request answering phase''' - the operation center has received no concrete booking, but a general inquiy and can communicate on this request with the travel agent or pax. This phase does not have a structured handling path		# '''General request answering phase''' - the operation center has received no concrete booking, but a general inquiy and can communicate on this request with the travel agent or pax. This phase does not have a structured handling path

Line 24:		Line 24:
	== Data domains & Perspectives ==		== Data domains & Perspectives ==
	A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on [[SARA data domains]] for further details.		A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on [[SARA data domains]] for further details.

	~~Each data domain has~~

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

	* [[Kordeus.PAX]]		* [[Kordeus.PAX]]
			* [[Travel assistance service request case]]

Stefanseiler: /* Data domains */

2025-06-26T06:20:55Z

Data domains

← Older revision		Revision as of 06:20, 26 June 2025
Line 22:		Line 22:

	* '''Transformation''' - the general inquiry can be change to a regular request, if the PAX adds a journey and booking during the inquiry process. In that moment, the decision the process will continue with the decision preparation phase of the regular request.		* '''Transformation''' - the general inquiry can be change to a regular request, if the PAX adds a journey and booking during the inquiry process. In that moment, the decision the process will continue with the decision preparation phase of the regular request.
	== Data domains ==		== Data domains & Perspectives ==
	A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on [[SARA data domains]] for further details.		A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. See this article on [[SARA data domains]] for further details.

			Each data domain has

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

	* [[Kordeus.PAX]]		* [[Kordeus.PAX]]

← Older revision		Revision as of 07:10, 26 June 2025
Line 25:		Line 25:
	A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. This results in different perspectives and tools for request processing:		A [[Travel assistance service request\|travel assistance service requests]] holds these data domains, which are each handled differently due to the ownership and sensitivity of contained information. This results in different perspectives and tools for request processing:

	* [[TASR - Travel agent perspective\|Travel agent perspective]]		* [[TASR - Travel agent perspective\|Travel agent perspective]] - The travel agent only has proprietary information on grouping of his customers. The case handling acts on behalf of the passengers, so they have the patient's perspective once the enter a specific case
	* [[TASR - Passenger perspective\|Passenger perspective]]		* [[TASR - Passenger perspective\|Passenger perspective]] - The passenger has to provide the request and required information for getting the approval for its requests.
	* [[TASR - Operation center perspective\|Operation center perspective]]		* [[TASR - Operation center perspective\|Operation center perspective]] - The OC recieves information and has to come to the point of approval or rejection of the request. Once this point is received it has to govern the assistance service delivery process and needs to instruct and monitor the partners finally delivering the assistance services
	* [[TASR - Delivery partner perspective\|Delivery partner perspective]]		* [[TASR - Delivery partner perspective\|Delivery partner perspective]] - The delivery partners receive information from the OC when to delivery which service. They can accept/reject and request or provide more information on service delivery from the OC.

	You can read up this article on [[SARA data domains]] for further details.		You can read up this article on [[SARA data domains]] for further details.