LHG:Interface dependent use cases - Revision history

Stefanseiler: /* Scheduled for later phases */

2025-11-20T10:38:43Z

Scheduled for later phases

← Older revision		Revision as of 10:38, 20 November 2025
Line 41:		Line 41:
	* alternative flights presentation		* alternative flights presentation
	* default craft type detection		* default craft type detection
			This use case depends on the [[LHG:ONERES Interface\|ONERES interface]]

	====== Services availability check for general iquiries {{Yellow-Tag\|YellowText=Phase 2}} ======		====== Services availability check for general iquiries {{Yellow-Tag\|YellowText=Phase 2}} ======

Stefanseiler: /* Detection of rotational changes (pre-flight, after confirmation to PAX) */

2025-11-20T10:37:28Z

Detection of rotational changes (pre-flight, after confirmation to PAX)

← Older revision		Revision as of 10:37, 20 November 2025
Line 28:		Line 28:
	When a request comes in, the team needs to check if the segments do have '''sufficient capacity''' for the itinerary's segments to support the requested services. For this, SARA should show the available bookable capacity (GAV) in the required booking class.		When a request comes in, the team needs to check if the segments do have '''sufficient capacity''' for the itinerary's segments to support the requested services. For this, SARA should show the available bookable capacity (GAV) in the required booking class.

			This use case depends on the [[LHG:ONERES Interface\|ONERES interface]]

			====== Retrive booking info from PNR / Booking Code ======
	This use case depends on the [[LHG:ONERES Interface\|ONERES interface]]		This use case depends on the [[LHG:ONERES Interface\|ONERES interface]]

Stefanseiler: /* Services availability check for general iquiries Phase 2 */

2025-11-20T10:04:43Z

Services availability check for general iquiries Phase 2

← Older revision		Revision as of 10:04, 20 November 2025
Line 31:		Line 31:

	== Scheduled for later phases ==		== Scheduled for later phases ==

			====== Flight plan data retrieval {{Yellow-Tag\|YellowText=Phase 2}} ======
			From the start the flight plans can be entered manually, but probably will not be entered, so a couple of functionality in the system will not be usable, e.g. :

			* flight number from Departure and Arrival port and departure time) and
			* alternative flights presentation
			* default craft type detection

	====== Services availability check for general iquiries {{Yellow-Tag\|YellowText=Phase 2}} ======		====== Services availability check for general iquiries {{Yellow-Tag\|YellowText=Phase 2}} ======

Stefanseiler: /* Use-Cases with SARA */

2025-11-20T10:01:55Z

Use-Cases with SARA

← Older revision		Revision as of 10:01, 20 November 2025
Line 1:		Line 1:
	~~== Use-Cases with SARA ==~~		This holds a list of all use cases, where interfaces play a important role.

	=== Phase 1 ===		== Phase 1 ==

	====== Detection of rotational changes (pre-flight, after confirmation to PAX) ======		====== Detection of rotational changes (pre-flight, after confirmation to PAX) ======
Line 15:		Line 15:
	This use case depends on the [[LHG:DAS Interface\|DAS interface]].		This use case depends on the [[LHG:DAS Interface\|DAS interface]].

	====== ~~Service~~ availability check for SAR (before confirmation to PAX) ======		====== General service availability check for SAR (before confirmation to PAX) ======
	When a request comes in, the team needs to check if planes operating the passengers itineraray's segments do support the requested services. For this, SARA should show the plane type (planned or if available operating). This allows the team to immediately see and SARA to detect incompatibilities before confirming the service to the PAX.		When a request comes in, the team needs to check if planes operating the passengers itineraray's segments '''do support''' the requested services. For this, SARA should show the plane type (planned or if available operating). This allows the team to immediately see and SARA to detect incompatibilities before confirming the service to the PAX.

	Required data for this use case:		Required data for this use case:
Line 23:		Line 23:
	* (optionally if already available) operating craft type		* (optionally if already available) operating craft type

			This use case depends on the [[LHG:ONERES Interface\|ONERES interface]]

			====== General seat availability check for SAR (before confirmation to PAX) ======
			When a request comes in, the team needs to check if the segments do have '''sufficient capacity''' for the itinerary's segments to support the requested services. For this, SARA should show the available bookable capacity (GAV) in the required booking class.

	=== Scheduled for later phases ===		This use case depends on the [[LHG:ONERES Interface\|ONERES interface]]

			== Scheduled for later phases ==

	====== Services availability check for general iquiries {{Yellow-Tag\|YellowText=Phase 2}} ======		====== Services availability check for general iquiries {{Yellow-Tag\|YellowText=Phase 2}} ======

Stefanseiler at 09:23, 20 November 2025

2025-11-20T09:23:26Z

← Older revision		Revision as of 09:23, 20 November 2025
Line 13:		Line 13:
	* operating craft type		* operating craft type

	This use case depends on the [[LHG:Interface ~~DAS via Kafka~~\|DAS interface]].		This use case depends on the [[LHG:DAS Interface\|DAS interface]].

	====== Service availability check for SAR (before confirmation to PAX) ======		====== Service availability check for SAR (before confirmation to PAX) ======
Line 40:		Line 40:

	* [[LHG:ONERES Interface]]		* [[LHG:ONERES Interface]]
	* [[LHG:Interface ~~DAS via Kafka~~]]		* [[LHG:DAS Interface]]

Stefanseiler at 09:22, 20 November 2025

2025-11-20T09:22:13Z

← Older revision		Revision as of 09:22, 20 November 2025
Line 35:		Line 35:
	* (optionally if already available) operating craft type		* (optionally if already available) operating craft type

	This use case depends on the [[LHG:Interface ~~ONERES~~\|~~Interface~~ ONERES]]		This use case depends on the [[LHG:ONERES Interface\|ONERES interface]]

	== See also ==		== See also ==

	* [[LHG:Interface ~~ONERES~~]]		* [[LHG:ONERES Interface]]
	* [[LHG:Interface DAS via Kafka]]		* [[LHG:Interface DAS via Kafka]]

Stefanseiler: Created page with "== Use-Cases with SARA == === Phase 1 === ====== Detection of rotational changes (pre-flight, after confirmation to PAX) ====== Operational changes can have heavy impact on a PAX journey, especially when it comes to mountable devices (stretcher, wenol) or extra-seats. Mountable devices may not me mounted directly before the flight, but eventually already one flight before. If the plane changes for a PAX, this might mean that the mounted device might not be available fo..."

2025-11-20T09:20:40Z

Created page with "== Use-Cases with SARA == === Phase 1 === ====== Detection of rotational changes (pre-flight, after confirmation to PAX) ====== Operational changes can have heavy impact on a PAX journey, especially when it comes to mountable devices (stretcher, wenol) or extra-seats. Mountable devices may not me mounted directly before the flight, but eventually already one flight before. If the plane changes for a PAX, this might mean that the mounted device might not be available fo..."

New page

== Use-Cases with SARA ==

=== Phase 1 ===

====== Detection of rotational changes (pre-flight, after confirmation to PAX) ======
Operational changes can have heavy impact on a PAX journey, especially when it comes to mountable devices (stretcher, wenol) or extra-seats. Mountable devices may not me mounted directly before the flight, but eventually already one flight before. If the plane changes for a PAX, this might mean that the mounted device might not be available for the PAX. So SARA needs to notify MOC if any rotational change has occured, which holds a passenger with a SAR request bearing one of these services.

Example: PAX is on a flight EWR to MUC, OUtbound stretcher mouting in MUC happende on plane with tailcode LHFBG. Not the plane had to return to MUC and instead operations team decided that the plane with tailcode LHODB will operate the flight EWR to MUC. This means that not stretcher is available for the passenger. This needs ad-hoc management action with MOC. Purpose of SARA is to notify the MOC team immediately before any of these changes immediately, so that they can react, e.g. with rebooking of passenger.

Required data for this use case:

* Flight plan with planned craft type
* operating craft type

This use case depends on the [[LHG:Interface DAS via Kafka|DAS interface]].

====== Service availability check for SAR (before confirmation to PAX) ======
When a request comes in, the team needs to check if planes operating the passengers itineraray's segments do support the requested services. For this, SARA should show the plane type (planned or if available operating). This allows the team to immediately see and SARA to detect incompatibilities before confirming the service to the PAX.

Required data for this use case:

* Flight plan with planned craft type
* (optionally if already available) operating craft type

=== Scheduled for later phases ===

====== Services availability check for general iquiries {{Yellow-Tag|YellowText=Phase 2}} ======
For general inquiries MOC team wants to check, which flights are generally available. For each of these flights they need to check the planned or operating craft type and will from this see for which of the generally available flights, this service is supported.

Required data for this use case:

* Flight plan with planned craft type
* (optionally if already available) operating craft type

This use case depends on the [[LHG:Interface ONERES|Interface ONERES]]

== See also ==

* [[LHG:Interface ONERES]]
* [[LHG:Interface DAS via Kafka]]