Interfaces
Interface catalogue
IATA MRO SmartHub provides interfaces for all modules (except Auctioneer). The API documentation pagee lists all available interfaces and specifies integration types and details about the respective interfaces and data models:
Integration types
The depth of an integration can depend on the customer specific requirements and varies from less complex manual data uploads using the UI or FTP up to automated and seamless interfaces via web services. This chapter illustrates integration types including examples, provides estimations for the efforts of integration and characterizes a typical integration project in scope and staff.
Web UI - Manually uploading CSV files via browser
To allow access to all core functionalities (e.g., request FMVs, trade inventory) of the platform, customers may use the manual file upload functionality (xml, csv, …) by using the graphical user interface. This enables a provision of the customer’s historical data which will be repeated at specific intervals.
Customers using additional functionalities, such as the connector for trading purposes, will need to provide their most recent demand information or supply information, or both. This information can also be uploaded manually using the file upload functionality on the platform.
Using the manual upload functionality, customers can start working with the platform immediately without establishing a technical interface first.
The efforts related to this minimal integration typically do not exceed more than 1-2 weeks, which includes familiarizing with the platform and data preparation. More details about this integration type can be accessed via the documentation for the different modules: Connector, Evaluator, Consignment, Auctioneer.
sFTP file transfer - Simple and semi-automated integration
A simple way to reduce manual work, is to use automated sFTP uploads with CSV files. IATA MRO SmartHub supports sFTP for all data types. Data specifications can be found here: API documentation under Schemas
REST API - Seamless and full automated integration
Customers using additional functionalities of the platform (e.g., analytics, long-term-planning, maintenance events optimization, etc.) typically require an automated interface. In particular for customers using the connector functionality for optimized trading purposes, it is relevant to dynamically update the customer’s current part supply and/or demand on the platform. In addition to mandatory data sets (transaction data), further information is required, e.g., maintenance events, certificates, part history and information.
In order to ensure a seamless update process, customers typically require a tailor-made or standardized interface to their ERP system or a related middleware. The efforts related to this integration type depend on the customer’s individual IT and business requirements. The chapter “Technical interfaces” provides details of all available services from which the customer may estimate their individual complexity.
The efforts related to this seamless integration normally do not exceed more than 2-4 months.
A full API documentation is available here: API documentation
Translation of internal company IDs
When using sFTP or Rest API to exchange listings data with IATA MRO SmartHub partner companies can be identified with internal company IDs/references. During the processing of the data these internal company IDs/references are translated into IATA MRO SmartHub internal company references. During the initial set up of a interface these translations are defined. It is possible to define separate company IDs/references for purchasing and selling.