In order to successfully work with FBO One, you will have to get used to the concepts and phrases it uses. One of these concepts is the handling order which is the starting point for every flight you will provide services for.
Conceptionaly, a handling order is just a container for everything that is related to a particular flight. Therefore it contains all details about the flight itself, such as information about its arrival and departure time, the aircrafts registration and type, the flight number, the crew and passengers, etc, etc. Associated with a handling order is a workflow. The workflow describes the possible stages a handling order can be in. For instance, when a handling order is created, it is in its initial stage which could be named 'Requested'. Depending on the actions you take, you can move the handling order through different stages until it arrives at an end state in which case the handling order is finished an the billing process of the client can start. FBO One allows for complete customization of workflows. Not only can you define the stages of the work flow, but also how to get from one stage to another stage (the transitions). You can define these stages and transitions in terms of how you have organized your business. As a side note, the Audit log traces you the journey of the handling order through the workflow, getting detailed information of who took which actions at what time.
TODO: insert handling order workflow and OTC workflow picture
A handling order also contains the services you or a third-party will provide for your customer when you handle their order. Common services are: fueling, cleaning, transportation of crew and passengers but also the handling of airport taxes. Associated with each service is a product which describes the actual service provided. Depending on the product, a service can also be associated with a workflow. Again, the workflows for products are completely customizable in FBO One following exactly how your business operates. It is the service that will keep track of the current state in of the workflow depending on the actions you perform on it.
TODO: insert a small service workflow
As services are part of the handling order, the handling order can of course not be finished unless all of its services are finished. Services themselves can contain other 'child' services creating hierarchies of services. This is a powerful concept that we will encounter in some of the examples given later on.
Services are sometimes also referred to as order lines. This is because the services are billed to the customer and are part of the handling order. Each service normally results in one or more order lines on the invoice. If present, then the pricing module is in charge of automatically calculating the price of a service. It it is not present, then a price can be entered manually for the service.
TODO: Insert picture diagram of a handling order
Handling order operational usage
Continue reading here on how to create and use handling orders in day-to-day situations.
Handling order administration
Continue reading here on how to setup handling orders and perform administrative tasks on them.