Our
Solutions
TripRecord and smartDOC introduce a streamlined and efficient SAP solution to handle the airline Direct Operational Charges (DOC) as part of SAP Flight to Settle process.
It is a comprehensive business and technology solution that enables the airlines to manage their Operational Charges, within the consolidated SAP system, using key connectors to common industry systems.
It builds in cloud and covers the creation of flight-operations-related data, its associated costs, accounting, accruals, and invoice processing.
TripRecord
Obtaining crucial operational data and analytics from different travel & transportation/airline services and support providers can be challenging, tedious, and can also take up a lot of company time and money.
By introducing a single generic API for all operational systems, Trip Record dramatically simplifies this process and provides a Single Source of Truth (SSOT) for applications and processes, thus reducing integration effort.
Trip Record runs on SAP Business Technology Platform (BTP); once integrated, you can access all the data and analytics you need.
Imagine how much it would cost you to integrate each service and support provider separately; You pay for the cloud resources that you use and nothing more.
smart DOC
The smartDOC solution enables you to automatically trigger the purchasing activities for a single flight and supports the creation of flight-operations-related data, its associated costs, accruals, and invoice processing, with a seamless connection to the Trip Record.
With smartDOC, you harness the power of TripRecord, Flight Acceptance Cockpit and Invoice Verification Cockpit to capture real-time data, use it to incur direct operational costs, and simplify the invoice verification and reconciliation process
The smartDOC is designed to address two main aspects:
Adapting the UI to the needs of the solution so that the following points are resolved:
-
Multiple screens/transactions.
-
Difficulty in maintaining master data
-
Extensive custom code was written to enable artificial connectivity between different modules (MM / PM / BRF)
-
Limited standard of master data migration tools
-
A complex set of roles and authorizations that do not match the needs of the solution
Consolidation of database architecture in order to reduce:
-
Artificial connections currently available in custom code between different modules (PM, MM, BRF)
-
A data structure based on a standard SAP data structure that does not overlap with LegState Flight solution
-
Low performance due to multiplicity of tables and objects
