LHG:Interface dependent use cases
This holds a list of all use cases, where interfaces play a important role.
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 DAS interface.
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.
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 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.
This use case depends on the ONERES interface
Retrive booking info from PNR / Booking Code
This use case depends on the ONERES interface
Scheduled for later phases
Flight plan data retrieval 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 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 ONERES interface