Connection details
Parameter |
Value |
Adresse |
sftp://upload.data.opremic.com |
Port |
2222 |
Username and password will be individually provided.
Upload process
Since the performance of uploads of large files largely depends on the available network connection, we implemented a two-step upload process. In the first step, all content data is transferred via sFTP. In the second step, the uploaded file is renamed to mark the end of the transmission.
Initially, the file must be uploaded with the file extension .tmp and after the transfer is completed, the file extension must be changed to .csv. This signalizes the system that this file has been successfully transferred and is now ready for further processing steps.
All uploaded files must be uploaded to the subfolder “upload” available on the sFTP server after login.
Connector
To show the same inventory to multiple companies a separate file specifying the material and individual pricing must be uploaded for every company. In case of a replacement operation, the IATA MRO SmartHub is taking care of the comparison and update operation between the existent stock and the newly uploaded stock.
Evaluator
There are no specific requirements to upload Evaluator files, as there are no dependencies between the different data types.
It is possible to split large data sets into multiple files to reduce the size of the files. The import process of IATA MRO SmartHub can identify the split data sets and re-combine them before importing them into the database.
File structure
The uploaded data file contains a header specifying the details of the upload and the actual data set. The header is stored in the first row of the data file as a JSON string.
Field name |
Description |
Allowed values |
|---|---|---|
type |
The type of data that is transmitted to the IATA MRO SmartHub in this file. |
Connector: consignment, inventory, purchaseorder, demands, pricerules. Evaluator: transactionhistory, workshophistory, materialgeneric, interchangeabilities Generic: aircraftfleetdata, enginefleetdata |
action |
Only relevant for Connector data. The type of action to perform for the data of this file. |
add, remove, replace |
visibility |
Only relevant for Connector data. Array containing your internal company IDs for which the uploaded inventory shall be visible. These will be matched to the respective companies on the IATA MRO SmartHub automatically. More information about the translation can be found here: Translation of internal company IDs. |
Internal company IDs as specified in your company systems and added to the Company ID translation of the IATA MRO SmartHub. |
The following example shows the header for an inventory upload that replaces your complete inventory on the IATA MRO SmartHub with the transmitted inventory and makes it available for the company with ID: internalID01.
{ "type": "inventory", "action": "replace", "visibility": "internalID01" }
Below is an example of the header for an Evaluator related upload:
{ "type": "transactionhistory", "action": "", "visibility": "" }
Beginning with the second line, the file must contain the actual data entries in CSV format. The separator can be comma (,) or semicolon (;). A specification of the expected columns and values can be found in the respective data requirement document.
File name
The final name of the data file needs to be:
[type]-[Company Name]-[Date]-[Counter].csv.
type The type of data that is transferred in this file. For a list of allowed values, please see section “File structure”.
Company Name Name of the uploading company, only lowercase letters without spaces.
Date Date of upload in format: YYYYMMDD.
Counter 4-digit counter that accounts for the number of files uploaded on the current day. The first upload starts with 0001. At midnight (CET), the counter is reset.
Test Company Ltd uploads a second file on 21 July 2020. The initially uploaded file has the file extension .tmp. After the successful upload, the file name is changed to: inventory-testcompanyltd-20200721-0002.csv
Filenames must only contain characters, numbers, and dashes. Spaces are not allowed. The usage of lowercase or uppercase characters does not matter.
Scheduling uploads / timetable
The schedule for uploads/data-updates depends on the customer and the data set. IATA MRO SmartHub can handle update cycles of uploading new files minute by minute or once a day. A recommendation of the update cycle for the Evaluator related data sets can be found in the data requirement specification. To ensure the correct processing of the files, the correct numbering of the “Counter” field in the file name must be ensured.
Technical contact
In case of technical questions during the onboarding project or any issues once the connection is productive, please contact Opremic trade GmbH, the technology partner of IATA for the IATA MRO SmartHub via the contact form contact form (How to contact IATA?).