Dev:Travel Segment Service Item Claiming: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
← Older edit
VisualWikitext
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
No edit summary
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
=== Prerequisites ===
=== Prerequisites ===
Once a ''PAX personal digital'' starts connects or is created at a [[PAX Portal|PAX portal]], it receives a list of all operation centers from the PAX portal. The personal digital uses the PAX portal to create and complete a [[travel assistance service request]].
Once a ''PAX personal digital'' starts connects or is created at a [[PAX.Portal|PAX portal]], it receives a list of all operation centers from the PAX portal. The personal digital uses the PAX portal to create and complete a [[travel assistance service request]].


=== Process ===
=== Process ===


# Once the ''personal digital'' decides to submit the request, it sends out the [[travel assistance service request]] to all known operation centers through the {{Blue-Tag|BlueText=MT-Message}} <code>TAC.TravelAssistanceRequest.Info</code>'''.''' It holds a [[Travel word definitions|travel itinerary]] consisting of multiple [[Travel word definitions|travel segments]] and a list of requested [[App:Travel assistance service administration|travel assistance services]].
# Once the ''personal digital'' decides to submit the request, it sends out the [[travel assistance service request]] to all known operation centers through the {{Blue-Tag|BlueText=MT-Message}} <code>TAC.TravelAssistanceRequest.Info</code>'''.''' It holds a [[Travel word definitions|travel itinerary]] consisting of multiple [[Travel word definitions|travel segments]] and a list of requested [[App:Travel assistance service administration|travel assistance services]].
# Upon arrival of this message, the [[Dev:Travel Assistance Service Request Operation Automation Engine (TASR-OAE)|Travel Assistance Service Request Operation Automation Engine]] analyses the request in these steps:
# Upon arrival of this message, the [[Dev:SARA.ProcessAutomationEngine|SARA.ProcessAutomationEngine]] analyses the request in these steps:
#* '''Compute embarcation and disembarcation points''' of this itinerary, as this is sometimes required for service devliery. Criteria: disembarkation port == last port of journey || disembarkation port != next segment boarding port ||  layover between disembarkation port and next embarkation time > 24h
#* '''Compute embarcation and disembarcation points''' of this itinerary, as this is sometimes required for service devliery. Criteria: disembarkation port == last port of journey || disembarkation port != next segment boarding port ||  layover between disembarkation port and next embarkation time > 24h
#* '''Compute relevant segments''', which this OC can claim. This is done, if it is authorative for the [[Travel word definitions|operator]] of this travel segment.  
#* '''Compute relevant segments''', which this OC can claim. This is done, if it is authorative for the [[Travel word definitions|operator]] of this travel segment.  
Line 12: Line 12:
#** by default set the status to created
#** by default set the status to created
#** check if the service is available on this segment. If the service is not available set the travel segment service item status to undeliverable.
#** check if the service is available on this segment. If the service is not available set the travel segment service item status to undeliverable.
#* Notify the PAX personal digital on the claimed services through sending an {{Blue-Tag|BlueText=MT-Message}} <code>TAC.TravelAssistanceRequest.ServiceSegmentItemUpdate</code>'''.''' It holds all segments, this OC is authorative for.
#* Notify the PAX personal digital on the claimed services through sending an {{Blue-Tag|BlueText=MT-Message}} <code>TAC.TravelAssistanceRequest.SegmentServiceItemUpdate</code>'''.''' It holds all segments, this OC is authorative for and the new status information on them.
#


 
=== Claim process status (on passenger side) ===
TravelAssistanceRequest is created  or updated in MOC Digital!
{| class="wikitable"
 
!Status
à Analysing itinerary
!Process status description
 
|-
·      
|Open for claim
 
|This SAR has been created, but has not been transmitted to the carriers
FRA-BEG (LH)
|-
 
|Claimed
à TAC.TravelAssistanceRequest.ClaimSegmentResponsibility
|This SAR has been created and has been submitted by the passenger. The request has been sent to the operation centers of the carriers. The request is waiting until all segments have been claimed by authorative operation centers (OCs)
 
|-
·       Number of irrelevant segments to which this OC is not responsible 2
|No OC Exists
 
|If all OCs answer "not responsible", then the status "No OC exists" will be set. This will trigger an email to PAX that this segment cannot be covered.
BEG-ZRH (LX), ZRH-FRA (LX) à TAC.TravelAssistanceRequest.NameSegmentResponsibleOCDigitals
|}
 
·       Subjourney detection
 
1. FRA-BEG
 
2. BEG-ZRH (LX), ZRH-FRA (LX)
 
Criterion:
 
·       Embarcation relevant ports à FRA (relevant), BEG (not relevant)
 
·       Disembarcation relevant ports à  BEG (relevant), FRA (not relevant)
 
à Create Travel Service Request in LH MOC FRA
 
à Create local segment based service product entries
 
·       segment x requested services
 
·       ditch segments, which do not support this service
 
à send to PAX Portal message, that service is not supported for this segment
 
·       For all other create segment-service-requests and associate them with the
 
Travel Service Request. Set status of segment-service-request to ”created”


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


* [[Dev:Travel assistance service requests - Process flow]]
* [[Dev:Travel assistance service requests - Process flow]]

Latest revision as of 05:39, 26 June 2025

Prerequisites

Once a PAX personal digital starts connects or is created at a PAX portal, it receives a list of all operation centers from the PAX portal. The personal digital uses the PAX portal to create and complete a travel assistance service request.

Process

  1. Once the personal digital decides to submit the request, it sends out the travel assistance service request to all known operation centers through the MT-Message TAC.TravelAssistanceRequest.Info. It holds a travel itinerary consisting of multiple travel segments and a list of requested travel assistance services.
  2. Upon arrival of this message, the SARA.ProcessAutomationEngine analyses the request in these steps:
    • Compute embarcation and disembarcation points of this itinerary, as this is sometimes required for service devliery. Criteria: disembarkation port == last port of journey || disembarkation port != next segment boarding port ||  layover between disembarkation port and next embarkation time > 24h
    • Compute relevant segments, which this OC can claim. This is done, if it is authorative for the operator of this travel segment.
    • For each relevant segment
      • create travel segment service items for each travel service to deliver.
      • by default set the status to created
      • check if the service is available on this segment. If the service is not available set the travel segment service item status to undeliverable.
    • Notify the PAX personal digital on the claimed services through sending an MT-Message TAC.TravelAssistanceRequest.SegmentServiceItemUpdate. It holds all segments, this OC is authorative for and the new status information on them.

Claim process status (on passenger side)

Status Process status description
Open for claim This SAR has been created, but has not been transmitted to the carriers
Claimed This SAR has been created and has been submitted by the passenger. The request has been sent to the operation centers of the carriers. The request is waiting until all segments have been claimed by authorative operation centers (OCs)
No OC Exists If all OCs answer "not responsible", then the status "No OC exists" will be set. This will trigger an email to PAX that this segment cannot be covered.

Related articles

Retrieved from "https://wiki.kordeus.com/index.php?title=Dev:Travel_Segment_Service_Item_Claiming&oldid=2512"