FBO One fuel module information sheet

This document describes the requirements of an FBO that uses FBO One for aircraft handling services. For fuel sales, an inhouse system is used.

The FBO is looking to replace their inhouse system with the FBO One fuel module.


Requirements coverage FBO One fuel module

Business overview

Business description

The fuel is supplied from a central fuel pool at the airport where the FBO's fuel trucks are refilled. The fuel then gets distributed to general aviation customers.

Type 1: Act as fuel service provider, delivering fuel on behalf of a broker or a fuel company

Type 2: Act as fuel service provider, delivering fuel on behalf of FBO.

Support for the given business types in FBO One

The FBO fully supports the sales types outlined in the business description. In FBO One, "Type 1" is called a "throughput" or "into plane" uplift. "Type 2" is called a "direct sale".

FBO One supports the fuel transactions visualized in the picture below. By tracking and reporting on all these types of transactions complete inventory control can be provided. It is also possible to use FBO One for uplifts only, for sales invoicing purposes.

Price calculation

FBO One works with the concept of price schemes for fuel. A price scheme defines how the price for the transaction is broken down in components.

A price scheme is automatically selected by the system. This done by looking for a price component in any of the price schemes that is specific to the debtor of the order.

Common price schemes are:

  1. Throughput fee, based for example on a hookup fee, a fee per liter or gallon, a certain minimum and maximum, and so on
  2. Cost-plus model (The FBO purchase price plus a contract differential)
  3. Market-price plus (market price, typically published by Platts, plus a contract differential)
  4. Posted airfield price model (post airfield price minus a contract or volume discount)
  5. Fixed price or ad-hoc price

Price components can also be created to define the applicable taxes, such as excise taxes and mineral oil tax.

Calculation for throughput

FBO One processes the purchase and uplift transactions as if the fuel was pumped directly from the fuel pool into the aircraft on behalf of the fuel supplier. An invoice is generated to the broker for uplifting the fuel, but not for the value of the fuel itself. The value of the fuel is invoiced by the broker to the aircraft operator.

For throughput, the delivery note the operator will not show the contract price. Only the uplifted gross volume is displayed:

The invoice to the broker or fuel supplier will show the throughput fee:

The price scheme in the above throughput example is selected because debtor "BP" has a contract price agreement for the "Jet A1 Uplift charge per unit" price component.

Calculation for direct sales

For direct sales by the FBO, the price scheme will be based on a contract differential. An example is displayed below:

The base price for fuel is based on a Platts market price, plus a contract differential. It is possible to insert additional price components at will. For example, to add a cost or purchase differential in addition to the contract differential.

In case the operator does not have a contract, a default differential can be applied. If needed, it is possible to hide the breakdown of the prices. In FBO One, this is called collapsing a group of line items on the invoice.

In the example below, a posted airfield price is calculated based on the same differential as in the example above, but it is hidden from the operator's invoice:

For analysis purposes, it is possible to view an expanded version of an order that has collapsed lines. This reveals the breakdown of the base price:

Payment options

In FBO One, forms of payment can be defined at will.

Credit types

Forms of payment have a credit type. The credit types are:

  • Direct. This covers direct payment before departure by the customer to the FBO, by means of cash or credit card
  • On account. This is used for on account customers that are invoiced. The payment conditions such as credit term are based on the debtors contract
  • Carnet. This covers payments cards that issued by brokers and fuel companies. FBO One will send an invoice to the debtor that underlies the form of payment.

Splitting charges between multiple related orders

Contracts for a debtor may be valid for a select group of products, such as Jet-A fuel, Avgas, anti-icing additive or handling charges. This is arranged by setting up contracts for the debtor for each of the product types.

When a payment form is selected for an order, line items on the order may automatically be moved to a related order. This logic is applied when the debtor has a contract that only covers a part of the services on the order. The services for which there is no applicable contract, can be paid separately on the related order. For example, if an operator has credit for handling services but not for fuel, the handling order will be created with all handling services on one order, and the fuel on a related order. The order with the handling services will have a form of payment of the credit type 'on account', such as BILL CHF. The fuel order will not have default form of payment. The user is alerted that the fuel order requires payment before departure. A form of payment for fuel is applied when going through the Take Payment process.

Currencies

Forms of payment also have a currency. All charges are converted to currency defined in the form of payment. FBO One reports revenue in both the charged currency as well as the currency that is used by the local accounting system.

Tracking payments and issuing receipts

FBO One tracks the payments that are made against an order in the front office. A payment record is created for all direct payments, and a receipt number is generated.

Online payments

Amsterdam Software is in the process of releasing a new online payment card validation function. The first card types that will be supported in Europe are the AVCard, US Government DESC Air Card and the MultiService Card. For FBO's in the USA, it is also supported to take online payments for regular credit cards.

The support for US Government Air Card will greatly simplify the invoicing process to US military and government flights. The US Government requires that all services on the invoice are codified according to their specification. This mapping of product codes will automatically be applied when executing a payment.

Using the online payment function in FBO One requires an third party agreement between the FBO and the online payment gateway processor AHT Services, LLC.

Existing refueling process description, and coverage of this process by FBO One

Step 1: Receive an order and refuel an aircraft

- A customer or a broker calls for fueling service

- A fuel truck gets allocated to the order and re-fuels the aircraft

FBO One coverage for taking orders and dispatching a fuel truck

When a request for fuel received, in can be that it applies to an aircraft for which there is already a handling request in the system for handling at the FBO. In this case, the uplift service will already be present in the handling order in FBO One, in the workflow state of 'Not started'.

In case the aircraft is not handled by FBO, but for instance is at another FBO or maintenance facility, a standalone fuel sales or can be created.

After the order is created, the uplift service is automatically added to it:

FBO One shows the pending fuel services in a dedicated fuel plan board. This can be used to dispatch fuel trucks to the aircraft. It is especially useful when the fueling staff is in a remote location and the business is very busy.

The status of all services, fuel as well as other services such as catering and de-icing, is displayed at the main front office Operations plan board: the OPS screen.

Finally, the OPS screen can also be displayed in an a layout for users of mobile touch screen devices. This is called the Ramp screen:

All screens have a powerful search function. As seen above, entering a fragment of the name of an operator or registration will display all orders that apply. It also possible to filter by service type, such as uplift or de-icing.

Step 2: Create Delivery Certificate, hand it over to the customer and update the software system

Existing business process prior to FBO One

  • During the re-fueling process, the fueler fills a paper based delivery certificate (a fuel ticket)
  • At the end of the refueling process, the delivery certificate is completed, signed and handed over to the customer. 
  • Completed delivery certificates are delivered to the back office where data is entered into the current IT system. 

The information from the delivery certificate entered is: 

  • Payment type (Fuel card or Direct Sales) 
  • Certificate Number 
  • Date 
  • Begin time of fueling
  • End time of fueling 
  • Aircraft Registration 
  • Fuel Truck Number 
  • Fuel type (Avgas / JET A1) 
  • Amount in liters (gross)
  • Fuel density (in kg/m3)
  • Fuel temperature (°C)
  • Calculated net liters at 15° C
  • Fueling tax relevant or not
  • Invoice number
  • Provider (MRO or other FBO company, which brokered the client)
  • Client (sold-to-party)

FBO One coverage for recording a fuel ticket

When FBO One is used the fuel transaction can be recorded in a number of ways:

  1. The fueler writes the paper based ticket first, and he then enters the information in FBO One as soon as he returns inside. If there is not much time available, he can radio the information to the operations department in the FBO, or enter the data himself using a mobile device such as a smartphone, a tablet computer or a computer mounted in the cabin.
  2. In case the truck is equipped with an electronic meter with a wireless link, the data can be sent directly into FBO One. The fueler enters the aircraft registration code in the fuel truck meter, which then sends a ticket that contains the truck number, meter counts and temperature to FBO One. In FBO One, the ticket can then be completed for any additional information that was not keyed into the electronic meter, such as the tax exemption status.
Payment alerts

At all times FBO One alerts the user about the credit status of the client. This way the fueler will be properly informed if a payment needs to be taken or not.

Entering a fuel release

When a broker or MRO company sends a fuel request by email, they will declare that the invoice can be sent to them. This type of message is called a fuel release. To enter a fuel release in FBO One, use Pay command that is available in the order screen. In the Pay screen, select 'On account or fuel release' to enter client that issued that fuel release:

The user can enter the client that issued the fuel release. They will be set as the debtor for the order and will be invoiced for the fuel. In the example below, the fuel release was given by UV Air.

Because in this example UV Air only has a contract for fuel, the fuel is split to a new order. The fuel order no longer shows a payment alert. The order that holds the handling charges will still need to paid later on.

Entering the ticket

Once the uplift is completed, the ticket can be entered in FBO One.

The values that are displayed and recorded in the ticket can be configured per FBO and per type of fuel (such as Jet A and Avgas).

As can be seen above, FBO One can record the gross volume, density and fuel temperature. Conversion and reporting is available to convert to any net or gross volume or weight unit of measure.

Using a wireless link for reading fuel tickets

If the fuel trucks are equipped with electronic meters with a wireless connection, FBO One can import those tickets.

The operations screen shows a shortlist of all tickets that have been newly imported from the electronic readers. As soon as the imported ticket is assigned to an order, it is removed from the list:

When entering a ticket in order, the imported ticket can be selected. This greatly reduces the time and effort needed for data entry:

FBO One currently supports importing tickets from the EMR3 meters by Veeder Root. Importers for other electronic meters will be developed as needed.

Processing a payment

After the refuelling, a payment card may be processed. This can either be a direct form of payment such as cash or credit card, or a carnet that is issued by a fuel broker or oil company.

Processing a credit card payment

Below is a sample order for which the operator has no credit. The screen shows "needs payment". A payment can be recorded using the Pay button.

This brings the user to the below screen, where the method of payment can be selected. The payment is processed offline; using a point of sales device that is not connected to FBO One.

Because a credit card (Visa) is used, both the handling and the fuel charges on the order are paid together:

Once the payment is completed, FBO One offers the user to print or email the handling order with the receipt.

The receipt for the captain is printed a the bottom of the handling order. It also shows that the balance due for this order is now 0.

Processing a fuel card card payment

When a fuel card (a carnet) is processed, it depends on the contracts of the broker or oil company that issued the card which products can be paid with the card. In the below example, the card is only valid for fuel:

This will result in a split of the handling order into two related orders. The first order will contain the handling services and still needs payment. The debtor for that order will remain Gulfstream Aerospace. The second order will contain the fuel and will be billed to BP. The captain receives a handling order that does not show the price that will be charged to BP. Fuel card payments are very similar to entering a fuel release, that was described in the previous section.

Step 3: Provide Delivery Certificates daily to the fuel provider and run daily reports

Current business process

All the physical delivery certificates are provided daily to the central fuel pool at the airport. By doing that, the fuel provider has the information which throughput sales have been performed, which direct sales have been performed by the FBO.

Daily reporting and inventory control coverage in FBO One

Reviewing stock and missing tickets

The fuelers in the front office are responsible for entering all tickets accurately. In order to validate that all tickets for the day have been entered correctly, FBO One provides a running stock overview. It shows for each truck if there are any missing tickets or other discrepancies. For example, it shows if the sum of all transactions for a fuel truck does not cause the calculated total quantity of fuel in the truck to fall below 0, or above the capacity of the truck.

The running stock screen below shows an alert for a gap in the meter counts. This indicates that at least one ticket is still unaccounted for.

The running stock calculation is based on all stock mutations, including

  • Uplifts
  • De-fuels
  • Transfers between trucks
  • Drain of fuel from a truck to a sump, for example for quality measurement.
  • Stocking takings. By entering a measurement of the physical quantity that is measured to be in stock for a truck, the quantity in stock is adjusted. The difference between the calculated quantity and quantity in the stock taking, can be booked by FBO One as a profit or loss margin at the end of the accounting period.
Daily stock mutation report
Once the running stock overview indicates that no errors exist in the inventory, a report can be downloaded and sent to the management of the fuel pool and to any other stakeholders at the FBO.

The screenshot below shows how to run a stock mutation report:

The report out below shows a selection of the columns available for the stock mutations report:

The dataset that feeds the stock mutations report, can be used to create all periodic fuel reports.

Flexible reporting engine in FBO One
FBO One allows for reporting to an Excel file. The reports can be setup in a number of ways:
  • Reports can be pre-defined by the user
  • The columns in the report on can be selected at will. There is choice of many datasets, such as the stock mutations as shown in the report above, as well as for example movements, orders and services.
  • It is possible to upload a nicely formatted Excel file into FBO One. This allows reports to show sub totals, totals, filters, charts and pivot tables. These templates can for example be used to generate a formally styled mineral oil tax statement.
  • It is possible to send reports by email automatically. The schedule and the email addresses of recipients can also be defined. Reports that are sent by email can be sent in Excel file layout, as well as in PDF format.

The below screen shot shows how a custom report can be added to FBO One. In this case, it is a report that will be attached to fuel invoices, and that lists all stock mutation in an excel file layout for easy processing by the client.

Step 4: Periodic reports

Current business process

Periodically the following reports are run:

  1. Sold fuel per a period, per fuel card provider and day
  2. Sold fuel per day and registration
  3. Fuel inventory, received fuel from the pool versus sold fuel + fuel in trucks
  4. Fuel sold which is exempt from mineral oil tax.
  5. Daily inventory calculation (calculated at both net volume at 15 degrees and gross volume at actual fuel temperature)

Coverage in FBO One

Sold fuel per a period, per fuel card provider and day.

This report can be defined with filters on the stock mutation report as shown above, on the columns form of payment, throughput and debtor.

An Excel template can be setup to generate exactly the layout of the current business process.

Alternatively, the data be summarized using pivot tables.

A pivot table can list the stock mutations by day, and filter by throughput status.

A similar pivot table can be defined that shows the data grouped by form of payment.

 

Sold fuel per day and registration

Fuel inventory, received fuel from the pool versus sold fuel + fuel in trucks

To ensure that the fuel supplied from the fuel pool matches the fuel sold, plus the fuel on stock, the running stock overview is the most suitable function. It shows if all stock mutations are properly accounted for, even including differences caused by physical stock takings, aircraft de-fuelling and drains from a truck to a sump.

The total amount in each truck after each stock mutation is displayed in the 'in stock usg' column in the screenshot above. The unit of measure to be use for this column, can be configured between usg and liter per FBO and per fuel type.

Furthermore, all delivery reports from the fuel pool to the trucks can be checked by reporting on the purchase stock mutations:

Uplifts that are exempt from mineral oil tax

Mineral oil tax is called excise or duty tax in FBO One. FBO One can calculate if duty tax applies, based on the destination of the flight, and the status of the operator as either a commercial operator or a private operator, as well as their country of domicile. Amsterdam Software also develops plug-in calculators for this type of dedicated calculation rules, for example the Swiss Duty Tax calculator or the Dutch Fuel Duty Calculator.

The same is true for value added tax (VAT) and General Sales Tax (GST), this is applied automatically based on the properties of the destination and the operator and is supported by custom calculators.

A report for the mineral oil tax statement to be paid and to be claimed can be setup based on a selection of the data in the stock mutations report. Include the columns duty to be claimed, duty to be paid and exchange rate differences.

Step 5: Sales order creation process

Existing business process prior to FBO One

All data from the fuel tickets gets transferred into our current billing system (SAP). This includes:

  • Sold-to-party number
  • Bill-to-party number
  • Payer number
  • Ship-to-party number (with Amount, Material Number)
  • Quantity and delivery Date
  • Invoice date
  • VAT tax indicator
  • Mineral oil tax indicator
  • Delivery Certificate Number.

The SAP Sales Order is then the basis to create the SAP invoices.

Creating sales orders in FBO One

FBO One integrates the inventory tracking and reporting with creating sales orders and invoicing. There is no need to re-enter the data.

In the section 'receiving an order' above, the process to create a handling order or a standalone fuel sales order has already been outlined.

The screenshot below shows a fuel sales order in FBO One.

As can been seen in the screenshot, the sales order screen in FBO One can warn the staff about any missing tickets in the running stock. Also, warnings are displayed in case of discrepancies in the duty (mineral oil) tax exemption indicator in the fuel ticket, compared to the client record.

Workflows for services, orders and invoices

FBO One is built around workflows. Workflows can be customized to match the services and order types at the FBO.

Examples for service workflows in FBO One are

  • Fuel uplifts
  • Aircraft de-fuelling
  • Purchase/delivery of fuel 
  • Inhouse transfers between trucks and stock locations.
  • GPU
  • Catering
  • Pax and crew boarding
  • Third party deliveries

FBO One allows for creating product and workflow definitions at will.

The workflow for a Jet fuel uplift service, will typically be defined as follows.

A fuel service can be added to a standalone fuel sales order, or to a full handling order. The difference between these two order types is that the fuel order does not track arrival and departure information, such as passenger count and arrival and departure time.

On a handling order, a number of services and charges will be auto-added, such as an uplift, the handling fees and parking charges. When a fuel order is created, only an uplift will be auto-added. The auto-add logic in FBO One is capable of detecting the fuel type of the aircraft. Therefore, an aircraft that requires AVGAS will have an AVGAS Uplift added to its handling or fuel order, and an order for a jet engine aircraft will get an Jet A Uplift.

Step 6: Sales invoices

Existing business process prior to FBO One

Type of invoices/credit notes:

1. Invoice for one fuel order in case of credit card or cash payment. Note: If the customer needs to have an invoice before departure, a FBO One handling order is handed over to the customer as pro-forma invoice.

2. Monthly invoice to charge fuel providers the commission and into-plane fee. This process gets applied in case the customer paid with a fuel card (or by a fuel release).

3. Monthly invoices for fuel sales to a number of customer where we contractually agreed to charge monthly

4. Yearly credit notes for commissions to broker partners

Note: All invoices and credit notes are created centrally in the central accounting back office that is separate from the FBO

Requirements:

  • It would be ideal for efficiency to generate the invoices out the fuelling system (FBO One)
  • Finance controlling and the dunning process will still be done from the central back office using the current accounting software (SAP)
  • A data load load function must be implemented to load invoices from FBO One into the accounting software

Coverage of the sales invoice process in FBO One

Once an order is completed by the front office staff, it is handed to over to the back office by 'registering' the order. The registered status is the first state of the back office workflow. As with any workflow in FBO One, the back office workflow can be adjusted if needed. Typically, the back office workflow has the following flow:

The back office workflow supports the following activities:

  1. Ensuring that each order is approved by a back office staff member. FBO One can place authorization based on user roles on workflow transitions such as the approve step. This enables segregation of duties: The system enforces that before invoicing, another person than the person who created the order reviews if the order has been correctly entered. Typical checks to perform are validity of the client's VAT and duty tax status, and checking against supplier delivery notes. FBO One has a powerful audit log, that logs all activities in the system. It can be used to analyze which person created and updated the order and its services, and which person approved it in the back office.
  2. In some cases, suppliers such as catering companies or ground transport companies do not deliver their invoices directly to the front office operations desk. Instead, they are sent to the FBO's back office after the aircraft departure. In these cases, the 'awaiting supplier invoice' status can be used. FBO One supports quick data entry of any pending charges by filtering based on the supplier. FBO One also supports to split any charges that have a pending charge to a related order. This way, the charges that are already know can be invoiced without waiting for the followup invoice that contains the third party disbursement.
  3. Once approved and completed, orders can be invoiced. An invoice can be created for one or multiple orders in one go. The system will automatically group orders on a single invoice or split them over multiple invoices based on the debtor's preferences, and currency and credit terms for handling or fuel.
  4. Once an order is invoiced, it is possible to create a credit note for it. This 'credit order' starts in the registred state and it can be invoiced using the regular workflow. When credit orders are created, FBO One can also create a copy of the original order in addition to the credit order. This copy allows for adjusting the order that was credited. For example, if the debtor was specified incorrectly in the original order, the copy can be used to send an invoice to the correct client.

The below screen shows how to invoice multiple orders at once:

Support for various types of invoices

As can been seen in the screenshot above, invoices are generated regardless of the form of payment.

1. Cash or credit card

In case the order has already been paid in full or in part by cash or credit card, an invoice is still generated. The amount of the payments received is subtracted from the grand total and displayed as the amount due. Even though invoices that cover credit card payments may actually not be sent to the debtor, the invoices are still generated in order to be able to book them in the accounting system.

2. Orders paid by fuel cards or by fuel release

Orders that are charged by a fuel card will be billed to the debtor that is setup for the fuel card. Depending on the type of fuel contract for each debtor, the charges of the fuel uplifts are based on a throughput price scheme or on a direct fuel sale by the FBO. The throughput price scheme can contain price components such as labor time, hook-up fee and fee per liter or per gallon.

3. Orders for clients that have credit with the FBO

Orders that are 'on account' will have a form of payment of BILL.

4. Broker commissions

In case a broker receives a periodic commission over the business that it generated, a standalone order can be created. The amount of the commission can be entered manually. It can be calculated by running a 'services revenue' report in FBO One, and use Excel for filtering and adding the amount for the broker.

Processing the invoices

Once an order or a group of orders is invoiced, one or more invoices are created. The screenshot above, 5 orders have been selected for invoicing. In our example, this results in 4 invoices:

The invoices for Shell have been grouped on a single invoice. This is arranged by setting up contract preferences for the client.

The invoices follow a workflow, as visualized below. Just as for any other workflow, it is possible to change the steps in the invoice workflow if needed.

In the invoice workflow, the invoices can be sent by email. If sent by hard copy only, the invoice status is still updated to the Sent status in order to track progress.

Fuel cost analysis and margin calculation

All deliveries into the FBO's inventory can be tracked. These are called fuel purchase orders.

These purchase orders can used to generate inhouse invoices, which can be exported along with the sales invoices to the accounting system. This allows for cost and margin analysis using the accounting system.

For FBO's that own their fuel inventory, cost analysis and margin calculation is also available in FBO One itself.

FBO One can calculate a profit margin or revenue for all revenue-holding fuel transactions. These are direct sales, purchases and aircraft defueling.

The margin is calculated as follows:

Margin = ([Unit price assigned to the fuel inventory] - [unit price of the fuel sold or purchased]) * Quantity

In addition to the margin, each transaction can have other revenues, such as an into-plane fee, hook-up fee, labor cost, duty tax and airport fees. These are excluded from unit price.

Throughput transactions need to be subtracted from the purchase orders. For throughput transactions, the quantity is counter booked against purchases, at the unit price that was assigned to the fuel inventory at the time of the uplift.

The picture below shows a sample of the applicable columns in the stock mutations report than are available for cost and margin analysis.

The unit price that is assigned the fuel inventory is updated every month. When the month is closed, the difference in value that occurs because of the newly assigned unit price is calculated by FBO One, and can be booked in the accounting system as the 'stock difference amount'. The actual value of the inventory is produced as well. An example of this stock revaluation entry that is produced when closing a month is shown below:

Loading invoices into the accounting system

After sending the invoices, they can be exported to an external accounting system such as SAP.

The invoices are booked in an entry period. Such a period corresponds to an accounting-system month. Periods can be opened and closed in FBO One by a finance manager.

The process of booking invoices results in the creation of an entry file. This is a file in Excel, PDF or a custom format that can be imported by the accounting system. Each back office in FBO One can have it's own export format for entries.

After the entry is created, the selected invoices are in the booked status, which is the last step of the invoice workflow.

Entries follow their own workflow, as follows:

In the created status, the export file is downloaded from FBO One by the user. He can then import the file in the accounting system. If the process of importing completes successfully, the user moves the entry into the Processed status.

Example accounting system entry of an uplift with duty tax

Duty tax (mineral oil tax) is charged to the customer:

Creating an invoice and booking on an entry generates an entry such as the one below:

The duty tax report is printed, by opening the entry period screen. This report is based on the stock mutations list, and uses a custom Excel template:

In the report, the duty tax claimed from the customer is listed:

When the entry period is closed, the duty tax to be paid to the tax office is booked:

IT and commercial aspects

How many customers run the FBO One fuel module in an operational environment?

FBO One is currently in use for fuel sales at

  • KLM Jet Center in Amsterdam and Rotterdam in the Netherlands (inventory control, costing and sales).

  • Bangor International Airport in Maine, USA. (inventory control, sales).

  • In May 2014, FBO One for fuel will be implemented at Jet Aviation Zurich in Switzerland (for sales).

  • ExecuJet in Zurich, Switzerland (sales)
  • Rss Jet Centre in Luton and Manchester, UK (sales)

  • Universal Aviation, Aruba (sales)

FBO One is in use at 85 airport FBO locations in total.

For how long is the FBO One Fueling system on the market?

FBO One is on the market for aircraft handling since 2007. FBO One Fueling was first implemented in 2011. Time line:

  • 2007: Release for handling and fuel

  • 2008: Links to EuroControl and NetJets Europe

  • 2010: Mobile and touch screen device screen layouts

  • 2011: Fuel sales and taxes, VAT

  • 2012: Inventory control (stock valuation, keep running stock, duty taxes, costing, gross/net density conversion)

  • 2013: Online credit card and aviation card payments

What is the pricing model for FBO One?

FBO One is charged per aircraft handling order. This includes all activities related to aircraft ground handling and refueling between arrival and departure.

Orders that are not related to aircraft handling, such as a standalone fuel sale, are charged at a lower rate.

How is the support concept?

FBO One is supported by a team of application support engineers and consultants. Day to day application and business support is mostly handled via email at support@amsterdamsoftware.com. Tickets are managed in salesforce.com. For urgents matters, a 24/7 telephone line is available that is relayed to the support engineer on duty. Engineers have access strictly for the purpose of providing your technical support and activities are recorded in the support ticket. Because of this access, analysis and issue resolution is very efficient.

For strategic matters, Amsterdam Software is available for meetings at most of the international conferences in the aviation industry. This is were we organize user group and individual meeting sessions. Amsterdam Software can be found at the annual conferences EBACE in Geneva, the NBAA annual conference in the USA, the Schedulers & Dispatchers conference in the USA, and the MEBA conference in Dubai.

Do you offer any functions for Sanctioned Party List Screening to avoid that we serve customers on the list

Yes. FBO One has an alert mechanism. Alerts can be placed in the bulletin board of each sanctioned customer account and will be displayed immediately upon viewing and creating orders.

Does the system offer a credit check function to check outstanding payments per customers?

In part. The system alerts of the credit status defined in the customers handling contract and fuel contracts. If there is no credit, the user is guided through the payment taking workflow. For on account customers, FBO One does not keep the actual amount outstanding. This function is supposed to be covered by the accounting system that manages the accounts receivable. The FBO One workflow ends as soon as the invoice has been sent to the client and the invoice is booked and exported to the accounting system. If a client exceeds their credit, it is the responsibility of the finance department to update the applicable contracts in FBO One and remove the credit term.

IT Security Aspects

Is your product cloud based or on premise?

FBO One is cloud based.

How is access control arranged?

How can we ensure that just we access our data?

FBO One has a detailed structure for authorization. Users are assigned to roles. Role permissions can be set per command, per entity (data type), and per front office FBO location, per back office administration, per type of order, and on workflows and workflow transition commands.

Is there there any of our data which other users of your system can see?

Each FBO network is managed in completely separate databases. Between these FBO-networks, absolutely no data is shared.

In case of an FBO network, users can be granted or denied access to the order history of each FBO based on their role in the system. This way, local staff for a particular FBO or back office can be restricted access to their own location. For FBO network sales and marketing purposes, the client and aircraft registration tables are always shared between all FBO's in the system.

The data that clients insert into the system is owned by that client. Amsterdam Software will only access the data for technical support directly related to FBO One.

About Amsterdam Software

Amsterdam Software business metrics April 2015

Staffing

  • For operations, the system is supported by

    • Radu Nitu, Auke Swart, Gabriel Jercan, and Ries Vriend (development and technical application and customer support)
  • For consultancy and training, the system is supported by

    • Richard Squires, Emma Squires, Connie Ingram, Ries Vriend
  • IT Operations / IT security

    • Kees Klinkenberg, Richard Lucassen, Ries Vriend
  • General management, finance and HR

    • Angela Schenk, Ries Vriend, Sukumar Shanmuganathan

Business metrics

  • FBO One related revenue 2014: 1.2 million euro

  • Shareholders: Ries Vriend (51%), World Fuel Services, Corp (49%). WFS can provide online payment processing for FBO One via its MultiService division. The company is listed on the new york stock exchange under the symbol INT. WFS has over 400 software development staff (mostly in their MultiService division) and provides transaction processing facilities similar to what FBO One offers in a number of industries (aviation, shipping, ground transport).

  • Partnerships: Amsterdam Software is a Silver Certified Partner of Microsoft for custom software development. Amsterdam Software and KLM Jet Center have a partnership for development of FBO One for aircraft handling and fuel.