top of page

Total Cost of Ownership

The following features allow us to provide the lowest TCO possible


Connectivity and installation

Connecting an airport on the iPort DCS network is simple and straightforward. A matter of defining 2 IP addresses and port numbers in the local firewall. An internet connection also suffices. iPort DCS customers at one airport benefit from the community model that allows sharing those connectivity costs.

Continuous Deployment

Only one client application exists. iPort DCS is very versatile, adapts itself to its environment and only requires one, initial installation. New functionality is published in small, digestible portions every 3 weeks. This limits the amount of time and cost required for maintaining various versions of the application.


e-Ticketing and IATCI included

Thanks to the close cooperation with Travelport, the iPort DCS deal includes free connectivity for e-ticketing and IATCI. The majority of reservation systems and DCSs are already connected with our ETKT and IATCI hubs. Additional airlines/systems can be connected against relatively low costs. 


One back-end logic for all channels

Software development costs are limited due to re-use of components. Counter, web and kiosk channels all use the same underlying components. Distinction is made only at the presentation level.



Outgoing teletype messages are included in the package. This is a component that is otherwise unpredictable, and often comes as an unpleasant surprise. In addition, iPort DCS provides the option to send IATA messages via email. The message router component supports a mix of teletype and e-mail addresses.



User training is considerably reduced thanks to iPort DCS's intuitive user interface. Seasonal workers can be used to bridge busy periods like the holiday season.


Passenger Self-service

Web check-in, kiosk, ancillary sales and bagdrop connection are also available via iPort DCS. These  are services that usually need to be built and maintained by an airline itself or a third party provider, which increases costs. By providing these services via a community model, costs for our customers are noteably reduced.

The usual charging structure applied by traditional DCS providers is based on a bottomline price per passenger. In addition to that cost, there are charges that may not always be controllable and predictable, such as teletype messaging costs. Or additional fees are required for automated boarding, e-ticketing and IATCI. Essential processes that - according to us - should be part of basic passenger handling fees. Comparing price per boarded passenger therefore is not always easy. It can be like comparing apples and oranges.

bottom of page