Services are the pricable entities. They are used in many tasks like pricing, operations, planning or performance measurements.
Service code, service description, service description in a second language, service unit group, service billing group and some other service characteristics like if the service requires time input and service application contexts are defined here.
In Celebris, there are two different context types which define the scope of defined services and packages. These are: landed and ground contexts. Landed context contains the aircraft information with either the arriving flight details, the departure flight details or both, along with ground details like the parking place, etc. Ground context includes only the ground related information of the aircraft and the arrival or departure flight information is out of scope.
The services can be marked to apply to a landed context, or a ground context, or both.
The services can be marked as obligatory according to their apply contexts or they can be priced accordingly in agreement definitions. Please look at the services and packages tab of the agreement screen.
The unit group definition specifies which unit codes are allowed to be used during service amount inputs and at their reporting. Because the cross conversion rates of the units in a group are predefined, different units from the same group can be used in service amount inputs at the service charge form window, at pricing definitions for the service, at any reporting about the service amounts and at the invoice service details. Celebris automatically handles the unit conversion.
Marking a service as "time input" enables the service charge form window to force the user to input the service start and end times.