11/2004 FL

Participant-Rules

Title, Age, Number

2.1.

1.	Title	Title of the passenger in the booking Adult  H, D Child  K Baby  B Lady  D Mr.  H Ms.  D Infant  B Example above: Rule is only fired for participants with title H,D in the booking
2	Age, Number	Age from – to Example above: Rule is only fired for participants with title H,D in the booking that are between 50 and 55 years old From – till Example above: Rule is only fired for participants with title H,D in the booking that are between 50 and 55 years old and that are the first or the second one of this attributes in the booking Total Example above: Rule is only fired for participants with title H,D in the booking that are between 50 and 55 years old and that are the first or the second one of this attributes in the booking; and when there are not more than 2 passengers with the Title ADULT in the booking.

Example in Genesis:
WHEN RULE IS FIRED passengers get 50% reduction:

WHEN RULE ISN'T FIRED passengers get no reduction:

Flag "All participants have to have the rule"

The system expects all participants assigned to a certain unit (room) to have this rule before it is fired:
Example in Genesis:
RULE ISN'T FIRED as certain passengers in the same unit are NOT ADULTS:

RULE IS FIRED as all passengers in the same unit are ADULTS, and for all of the passengers the rule is valid:

"Minimum Full Payer"

1.2.

1.

Min. full Payer

Number of passengers that must have NO RULE FIRED so that the rule can be taken for the declared passengers

Example above:
Rule is only fired for participants with title K in the booking that are the first or the second one of this attributes in the booking when there are 2 of that tilte in total and at least 2 persons on the booking that don't have any rule fired.

Example in Genesis:
RULE IS FIRED FOR BOTH CHILDREN as the two Adults pay full price (no rule taken for them)

Same happens if the Adults are in different units:

2.

Restriction on Min. full Payer

Full payers must be in the same unit!

Example above:
Rule is only fired for participants with title K in the booking that are the first or the second one of this attributes in the booking when there are 2 of that tilte in total and at least 2 persons on the booking that don't have any rule fired and that are in the same unit

Example in Genesis:
RULE ISN'T FIRED FOR BOTH CHILDREN as the two Adults that pay full price (no rule taken for them) aren't in the same unit

The FULL-PAYERS aren't in the same unit, therefore one Child has to pay FULL PRICE so that there are 2 FULL-Payers in the same unit. The second Child gets the rule fired as now there are two full-payers in the same unit (passengers 1 and 3)

"Min-/Max- Participants"

On unit-level

Example above:
Rule is only fired when there are at least 2 but not more than 3 passengers on the same unit (excluding children from calculation).

Example in Genesis:
RULE ISN'T FIRED for the children as there is only one participant in the unit that isn't a child.

RULE IS FIRED as there are two participants in the unit that are ADULTS:

Participant Code, Customer Request, Total Price dependend on participant price

3.2.1.

1.	Participant Code	Selection of participant-codes from basic-settings: Example above: Rule is fired when the participant-code "Busdriver" is assigned to a certain passenger (properties of passanger) of a booking. Remark: Participant-code can also be stored at the clients-profile and will be automatically assigned to a participant in Genesis if the passenger is selected through client-search.
2	Customer request	Selection of a certain customer-request-code If this code is booked on Service- or Participant-level the rule is fired
3	From-till	Entry for Travel-Insurance-calculation in german market Travel Insurance-calculation in dutch-market doesn't work through price-rules

Min-Max-Restriction on booking-level

Example in Genesis:
NOW THE RULE IS FIRED although the two adults are not in the same unit. The restriction is checked on booking-level and on that level it is fullfilled.

More than one Min-Max-Restriction

Min-Max-Restrictions can be combined with AND/ OR – relation
Example in Genesis:
RULE IS FIRED AS the second restriction is combined with OR and is valid:

Changing the relation to AND the RULE ISN'T FIRED anymore:

Unit-Rules

From-Till Units

The FROM-TILL Restriction allows to declare the number of units that needs to be booked so that a certain rule will be fired.

Example above:
Rule is only fired when there is ONE unit booked
Example in Genesis:
RULE ISN'T FIRED AS there are 2 units booked:

Changing the Units-Rule:

Same Booking fired the children-rules:

Amount Service

The Amount-Service-Field allows to restrict the number of servicelines for taking the rule

^

Example above:
The rule will only be taken when there are 2 service-lines of the service booked:
Example in Genesis:
RULE ISN'T FIRED due to more than 2 servicelines

For same kind of booking the RULE IS FIRED when there are not more than 2 servicelines:

"Each" and "once per booking"

This 2 fields are still not completely supported

IMPORTANT for UNIT-RULES

In case of the unit-related rules the calculation of prices strongly requires an exact and logic set-up and corresponcence of the TYPES of PRICES and the TYPES of PRICERULES:
The price the rule is related to should be based on UNIT
The price coming out of the rule should also be calculated on UNIT-base

Combination of Participant- and Unit-Rules

It is possible to combine participant- and unit-rules in certain cases:

Example above:
The participant-rule (reduction for adults of 55 or more years) will only be taken when there are 2 units of the service booked
Example in Genesis:
RULE ISN'T FIRED due to more than 2 units

RULE IS FIRED (only for the adult with 55+ years) if there are exactly 2 units booked

Time-related Rules

3.2.1.

1.	Days	Declaration of days that need to be included in the travel-date Example above: Rule is only fired if Monday is included in the traveldate
2	Specification of days	Check all days included  all flagged days need to be included in the travel-date Check min. one day included  at least one of the flagged days need to be included in the travel-date Check dep. Day included  the flagged days need to be departure-day Example above: Rule is only fired if Monday is departure day!

Example in Genesis:
RULE ISN'T FIRED as Monday isn't departure day:

RULE IS FIRED when flag for departure-day is deactivated:

Supllement for Monday forming part of the travel-date:

3

Calculation

Definition of the days that should be taken for calculation of the reduction/supplement:

All days system should take all days of the travel for calculation if rule is fired
Closed days  works in combination with flags "check all days included" and "check min one day included"; if one of this flags is set the INCLUDED (closed, sic!) days are taken for the calculation
Once  in case that the rule is fired the calculation of the reduction/supplement is only made once

Example above:
Rule is only fired if Monday is included in the traveldate, the amount is calculated only for this day (Monday)
Example in Genesis:
Supplement of 10 CHF for Monday being included in the travel-date

2.1.

1

Min. stay, max. stay

Declaration of the staytime

Example above:
Rule is only fired if staytime is 6 days

Example in Genesis:
Supplement of 10 CHF for first service is calculated as this one takes exactly 6 days:

2

Relation to travel-date

In case of assignment of the pricerule to a certain price in a certain season, the system will calculate over the season if this flag is set.

Example
Two different pricelines for two seasons, 5 days in one, 2 days in the other season 
GenVAS takes the min-max term-related rule as flag is activated

321

1	X-days for price of y-days	Declaration of the number of days to be paid to have certain number of days free Example above: Rule is only fired if 6 days are paid, next 4 days will be for free
2	Calculation	Declaration of the concrete days to be paid: Cheapest days  in case of season-crossing the cheapest days are taken for calculation of the reduction Cumulate  in case of season-crossing the system calculates an average of all day-prices to get the reduction First days, last days  the first days of the stay or the last days are for free Most expensive days  the most expensive days are for free
3	Once	Flag is set to make sure that the reduction is only taken once when the rule is fired If the flag is set: Stay of 10 days  6 days to be paid and 4 days for free Stay of 20 days  16 days to be paid and 4 days for free Example above: Rule is fired for very 10 days of stay

Example in Genesis:
Rule is FIRED twice for 22 days of stay, 8 days in the stay of 22-days are for free

Other Rules

Code-Combination

2.1.

1	Code	The code declared needs to be part of the service-type Example above: Rule is only fired if A11 is part of the requested servicetype
2	1:1	The code declared needs to be exactly the one requested in the booking If flag set: Example above: Rule is only fired if A11 the requested servicetype

Example in Genesis:
Rule is FIRED only for those services where A11 forms part of the accomodation

Airport

In case of Flights with departure from Mauritius and Airline AIR CANADA the rule is fired

More pricerules at the same time

There are certain possibilities to declare how the system should work when more than one pricerule is valid at the same time.
Example: Stay-related-rules and child-reduction
Rule 1: Stay-related rule that gives free-days in a certain staytime

Rule 2: Child-reduction-rule

Case 1: Both rules related to same basic-price

Both rules have the same calculation base: the basic price of the service:
Time-Rule: calculation of 8 free days à 10.-CHF = - 80/pax
Participant-rule: calculation of 10% reduction for the child = 10% of 220 CHF = - 22 /child

Case 2: stay-related rule before Participant-rule

The child-reduction-rule gets a higher calculation-level:
Higher calculation-level for the child-reduction-rule

Time-Rule (lower level) is calculated first: calculation of 8 free days à 10.-CHF = - 80/pax
Participant-rule (next higher level) is calculated on base of basic-price and Time-rule-calculation: calculation of 10% reduction for the child on the already reduced amount of the time-rule = 10% of 140 CHF = - 14 /child

Case 3: Participant-rule before stay-related rule

The time-related-rule gets a higher calculation-level:

Higher calculation-level for the time-related rule

Participant-rule (lower level) is calculated on base of basic-price: calculation of 10% reduction for child = 10% of 220 CHF = - 22 /child
Time-Rule (next higher level) is calculated on base of the already child-reduced price: calculation of 8 free days à 9,5.-CHF = - 76/pax

Case 4: stay-related rule before Participant-rule at the assignment of the pricerule

The time-related-rule gets a higher calculation-level:

Higher calculation-level for the time-related rule

But at the assignment of the pricerule the time-related rule gets lower level:

Time-Rule (lower level) is calculated first: calculation of 8 free days à 10.-CHF = - 80/pax
Participant-rule (next higher level) is calculated on base of basic-price and Time-rule-calculation: calculation of 10% reduction for the child on the already reduced amount of the time-rule = 10% of 140 CHF = - 14 /child

Case 5: stay-related rule beats Participant-rule

Without assignment of CALCULATION-LEVEL

Both rules are assigned to the same default-pricegroup „test"

During assignment of the pricerules the default-group is automatically filled:
No level defined
GenVAS now tries to get the best price inside of the group "Test" of pricerules, and that's the time-related reduction:

Including assignment of CALCULATION-LEVEL

If the calculation-level is assigned for grouped pricelines, the system also takes this into account for calculation of the BEST REDUCTION:

Calculation Bases

"Timeunit calculation base"

This particular price-rule-calculation-type is still not completely clear in its functionality

Participant / time unit
Quantity / time unit
Booking / time unit

Browser nicht unterstützt