Service (Glossary)

The service and product relationship

Services (also known as order lines) are central to the operation of FBO One. Services are added to a handling order and have an associated product. An example of a product is limousine service. This product can be added to a handling order and adds a service to this handling order. This limousine service also adds a limousine service workflow to the handling order that keeps track of the workflow associated with the limousine service. This makes sense, as providing for a limousine service is a workflow itself: you have to order the limousine from third party or an in-house department telling them when and where to pick up the passengers, you must receive a confirmation of this request, and finally confirm the delivery of the passengers. Without FBO One you will also have to make sure the customer is billed for the service and make sure the back office receives all information necessary for the invoice.

Before the entire handling order can be finished FBO One makes sure you also have finished every service you have added to the handling order, notifying you of pending actions of not-finished workflows.

Apart from real life products such as the limo service, fueling service or delivering catering products, FBO One also uses products for other things that are not immediately recognizable as a 'real life' products. Examples are airport taxes, environmental fees, landing fees and disbursements. These type of products don't 'feel' like real products at all! Yet, it is a clever trick of FBO One. In the end, when the entire order is handled, all products end up on the invoice of the handling order. Each and every product is represented on the invoice by one or more order lines, whether it is a real life product such as fueling service or as chargeable item such as an airport landing fee. That's exactly the reason why services are also known as order lines. Once you understand this dual nature of an FBO One product, things will start to get clearer.

From this we can conclude that some services need to be associated with workflows and for others (such as a landing fee, or an airport tax) they do not make sense.

Third party services are services that are ordered externally, so they will usually have a workflow and/or a supplier configured in order to keep track of the order and delivery status of the service.
Ramp services are executed on the ramp, so should have the 'Show in ramp screen' flag set. That way they will be visible in the Daily Service Summary and on the ramp screen.
Services which only add an order line or charge to the invoice, generally do not have a workflow associated with them.

See also

Edit services screen

Add services screen

Move services screen

Delete services screen

Service (Fields)

Order (Glossary)