09/MAR/2025 - Waterfall Nesting

Dear Customers,

We are excited to inform you about a new feature added to GO7 PSS that enables you to configure advanced class nesting, allowing you to set availability dependencies across multiple booking classes or create independent class structures.

Practical Use Cases

• No Nesting: Classes operate independently with no cross-impact on availability.
• Serial Nesting: A single booking in Economy Flex reduces seats in Economy Saver.
• Parallel Nesting: Business Flex and Business Saver manage inventory independently of Economy classes, even with shared constraints.
• Combination Models: Blend nesting with independence, e.g., keeping Premium Economy independent while nesting Economy classes.
• Complex Parallel Nesting: Multiple chains of nested classes operating side by side.

New functionality added to class setup:

• Nesting Enabled/Disabled: If marked, will act as a nested class and will be affected by other classes if no string is defined.
• Min Amount: A minimum number of bookings to allow this class to be sold.
• Max Amount: A maximum amount of bookings that, when passed, will close this class. 
• String of Nested Classes: A defined list of classes that are grouped and will only be affected by classes of the set string.
• Closed Class: Once checked, the class will no longer be available for further bookings.

Examples:

No Nesting

In this example, each class operates independently.

Bookings in one class have no impact on the availability of the other classes.

Serial nesting all classes nested

In this example, classes A, B, C, and D are interdependent.

Each class affects the other's availability based on active bookings.

• Class A has 2 active bookings.
• Class B has 1 active booking.
• Class D has 3 active bookings.

These active bookings impact the availability of all nested classes.

For instance:

• Class A’s availability is calculated as 25 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) – 3 (active bookings in D), resulting in 19 free seats.
• Class B’s availability is calculated similarly: 20 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) – 3 (active bookings in D), resulting in 14 free seats.

Serial nesting with independent classes

In this example, classes A, B, and C are nested, meaning they impact each other’s availability.

Class D, however, operates independently since nesting is not enabled for it.

• Class A has 2 active bookings.
• Class B has 1 active booking.
• Class D has 3 active bookings but and is not influenced by the nested classes because it is not part of the nested group.

The availability for the nested classes is calculated as follows:

• Class A: 25 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) – 3 (active bookings in D) = 19 free seats.
• Class B: 20 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) – 3 (active bookings in D) = 14 free seats.
• Class C: 15 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) – 3 (active bookings in D) = 9 free seats.

Class D’s availability is calculated independently as 10 (initial availability) – 3 (active bookings in D), resulting in 7 free seats.

Serial nesting with nesting string and independent classes

In this example, classes A, B, and C are part of the nesting string "ABC", meaning they are grouped and affect each other’s availability.

Class D, however, is independent and does not interact with the nested group.

• Class A has 2 active bookings.
• Class B has 1 active booking.
• Class C has no active bookings but is still affected by bookings in other classes within the "ABC" string.

The availability for the nested classes within the "ABC" string is calculated as follows:

• Class A: 25 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) = 22 free seats.
• Class B: 20 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) = 17 free seats.
• Class C: 15 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) = 12 free seats.

Since Class D is not a nested class, therefor, its bookings are independent and is not affected by the nested classes' availability.

Class D’s availability is calculated independently as 10 (initial availability) – 3 (active bookings in D), resulting in 7 free seats.

Serial nesting with parallel nesting strings

In this example, parallel nesting strings are implemented:

• Classes A and B belong to the "AB" string, meaning the are affected only by each other.
• Classes C and D belong to the "CD" string, meaning they are affected only by each other.

Bookings in one string do not impact classes in the other string, ensuring that the groups remain independent.

The availability for the "Parallel nesting" strings are calculated as follows:

String AB:

• • Class A: 25 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) = 22 free seats.
  • Class B: 20 (initial availability) – 2 (active bookings in A) – 1 (active booking in B) = 17 free seats.

String CD:

• • • Class C: 15 (initial availability) – 3 (active bookings in D) = 12 free seats.
    • Class D: 10 (initial availability) – 3 (active bookings in D) = 7 free seats.

This setup ensures that classes in the "AB" string affect only one another, while classes in the "CD" string are similarly isolated, enabling parallel nesting behavior.