Evaluator
This section specifies the content and process to contribute data to the IATA MRO SmartHub Evaluator. In general, six data sources are part of the data set requested by IATA. The following table outlines the sources and the contribution details.
Name |
Description |
Customer obligation |
Historical data |
Update cycle |
|
|---|---|---|---|---|---|
1 |
Transaction Event History |
Purchase and/or sale events for components, rotables, engine parts, airframe material, landing gear material, consumables or expendables; for any/all conditions and with all transaction partners. |
Mandatory |
Mandatory: 12 months / Recommended: 24 months |
At least monthly |
2 |
Internal Workshop Event History |
In-house workshop events for own material or material of customers, regardless of success of the event or task performed. |
Based on availability |
Mandatory: 12 months / Recommended: 24 months |
At least monthly |
3 |
External Workshop Event History |
External workshop events for own material or material of customers, regardless of success of the event or task performed. |
Based on availability |
Mandatory: 12 months / Recommended: 24 months |
At least monthly |
4 |
MRO Services Catalog |
Pricing catalog information for workshop events if available. Source for this data set could be, e.g., a repair catalog for external customers specifying the different events by scope and price. |
Based on availability |
Mandatory: 12 months / Recommended: 24 months |
At least yearly |
5 |
Part Information Catalog |
Generic information on parts from the material catalog. This includes but is not limited to material characteristics, technical details, and a list of internal possibilities for utilization of these parts. |
Mandatory |
Mandatory: 24 months / Recommended: 24 months |
At least quarterly |
6 |
Interchangeabilities & Modification Information |
Information about modification possibilities for parts and the possibility to interchange parts. |
Based on availability |
Mandatory: 12 months / Recommended: 24 months |
At least quarterly |
Data anonymization
In order to ensure the commercial confidentiality of all customers, data that has been uploaded to the IATA MRO SmartHub is pre-processed, validated, and anonymized before it is used in any visualization or calculation. During this pre-processing step, various consistency checks are applied and a quality assurance process takes place. Such a restrictive validation process ensures that resulting values are valid and not distorted by skewed input data. Personal information such as customer name are not relevant for the FMV (Fair Market Value) calculation process. Therefore, any data provided by customers will be anonymized. It is not possible to refer to any personal data provided via the platform.
Data transmission & data format
IATA always ensures that data contributed by customers to the IATA MRO SmartHub is secured and kept confidential. Processing, validation and anonymization of customer data takes place on servers in Germany. We offer a broad variety of interfaces to securely provide this data to the IATA MRO SmartHub. The most relevant three options to transmit the data sets are:
Option |
Description |
Format |
|---|---|---|
Via Web-uploader / Browser |
Data files are manually uploaded to a secured web platform via the browser. |
CSV, XLS, XLSX |
sFTP |
Data files are semi-automatically transferred from a customer server to a secured SFTP server. |
CSV, XLS, XLSX |
REST API |
Data sets are automatically sent to a REST API in machine-readable format. |
JSON |
The format of the data files and the individual fields is not fixed. To meet the individual requirements of IATA MRO SmartHub’s customers, the exact field names, data formats, and data types will be individually defined during the onboarding process.
The most important rule for uploading data is that the format of all uploaded files must remain consistent. Once a format has been agreed upon, this should not subsequently be changed. If you do, please contact IATA MRO SmartHub support before the changes take effect.
Preliminaries & clarifications
This section provides general guidance on the terminology used in the following. In this context, the necessity of contribution is specified based on the following categorization:
For all data fields that are not mandatory, the contribution is recommended if the data is available. These additional data fields can significantly improve the quality of IATA MRO SmartHub’s KPIs and the user experience on the platform. For example, including any information about locations (seller/purchaser/shop) will enable the IATA MRO SmartHub to consider distance related factors in TAT and lead time calculations. Providing further details on the part condition, e.g., cycles remaining, time remaining, date of manufacture, will improve the quality and accuracy of fair market values (FMV) calculated by the IATA MRO SmartHub Evaluator.
The utilization for each data field is differentiated as follows:
Utilization |
Definition |
|---|---|
QA |
Data is used as parameters for the mandatory internal quality checks. |
Algorithms |
Data is used as input for the internal algorithms. |
Visualization |
Data is used for visualization inside the web application. |
Protecting customer data is key for the IATA MRO SmartHub. All processes to receive, integrate, anonymize, and handle customer data follow strict rules to ensure confidentiality and protect sensitive information. For each data field, the accessibility and visibility within the IATA MRO SmartHub is determined by the group of viewers.
Visibility |
Definition |
|---|---|
Own company |
Data is only accessible by users of the same company. |
Other users |
After anonymizing this data field, the information is accessible by all users of the IATA MRO SmartHub Evaluator. |
Support/Contact
For general questions, please contact IATA via our our contact form. If you have any technical questions, please contact your onboarding manager from Opremic.
#1 - Transaction Event History
The API documentation can be found here API DOC Transaction Event History
The specification of the expected data formats and data types for CSV contributions is also documented on API documentation under Schemas -> Transaction Event History
Data Field |
Utilization |
Visibility |
||||
|---|---|---|---|---|---|---|
Name |
Mandatory |
QA |
Algorithms |
Visualization |
Own company |
Other users |
Part number |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Part manufacturer |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Part condition |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Quantity |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Unit |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Price |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Currency |
Yes |
Yes |
Yes |
NA |
NA |
NA |
Transaction date |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Transaction type |
Yes |
Yes |
Yes |
Optional |
Complete |
NA |
Incident related |
No |
Yes |
Yes |
NA |
NA |
NA |
List price |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Serial number |
No |
Yes |
Yes |
NA |
NA |
NA |
Date of manufacture |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Time remaining |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Cycles remaining |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Location of seller |
No |
Yes |
Yes |
Optional |
Complete |
NA |
Location of buyer |
No |
Yes |
Yes |
Optional |
Complete |
NA |
Date of delivery |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Part tag date |
No |
Yes |
Yes |
NA |
NA |
NA |
Identification key |
No |
Yes |
NA |
NA |
NA |
NA |
#2 – Internal Workshop Event History
The API documentation can be found here API DOC Internal Workshop Event History
The specification of the expected data formats and data types for CSV contributions is also documented on API documentation under Schemas -> Internal Workshop Event History
Data Field |
Utilization |
Visibility |
||||
|---|---|---|---|---|---|---|
Name |
Mandatory |
QA |
Algorithms |
Visualization |
Own company |
Other users |
Part number |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Part MFR cage code |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Condition after |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Condition before |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Task performed |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Quantity |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Unit |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Date event start |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Internal costs |
Yes |
Yes |
Yes |
NA |
NA |
NA |
Currency of internal costs |
Yes |
Yes |
Yes |
NA |
NA |
NA |
Event with replacement |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Scrapped |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Date event end |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
TAT |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Price |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Currency of price |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Serial number |
No |
Yes |
Yes |
NA |
NA |
NA |
Date of manufacture |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Time remaining before |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Cycles remaining before |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Shelf life remaining before |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Time remaining after |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Cycles remaining after |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Shelf life remaining after |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Location of shop |
No |
Yes |
Yes |
NA |
NA |
NA |
Identification key |
No |
Yes |
NA |
NA |
NA |
NA |
#3 - External Workshop Event History
The API documentation can be found here API DOC External Workshop Event History
The specification of the expected data formats and data types for CSV contributions is also documented on API documentation under Schemas -> External Workshop Event History
Data Field |
Utilization |
Visibility |
||||
|---|---|---|---|---|---|---|
Name |
Mandatory |
QA |
Algorithms |
Visualization |
Own company |
Other users |
Part number |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Part MFR cage code |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Condition after |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Condition before |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Task performed |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Quantity |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Unit |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
TAT |
Yes |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Price |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Currency |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Event with replacement |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Scrapped |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Date event start |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Date event end |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Date of shipping for event |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Date of shipping after event |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Serial number |
No |
Yes |
Yes |
NA |
NA |
NA |
Date of manufacture |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Time remaining before |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Cycles remaining before |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Shelf life remaining before |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Time remaining after |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Cycles remaining after |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Shelf life remaining after |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Location of shop |
No |
Yes |
Yes |
NA |
NA |
NA |
Identification key |
No |
Yes |
NA |
NA |
NA |
NA |
#4 – MRO Services Catalog
The API documentation can be found here API DOC MRO Services Catalog
The specification of the expected data formats and data types for CSV contributions is also documented on API documentation under Schemas -> MRO Services Catalog
Data Field |
Utilization |
Visibility |
||||
|---|---|---|---|---|---|---|
Name |
Mandatory |
QA |
Algorithms |
Visualization |
Own company |
Other users |
Part number |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Part MFR cage code |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Task performed |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Condition after |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Condition before |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Price |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Currency |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
TAT |
Yes |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Valid from |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Valid until |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Scope description |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Minimum logistics time |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Identification key |
No |
Yes |
NA |
NA |
NA |
NA |
#5 – Part Information Catalog
The API documentation can be found here API DOC Part Information Catalog
The specification of the expected data formats and data types for CSV contributions is also documented on API documentation under Schemas -> Part Information Catalog
Data Field |
Utilization |
Visibility |
||||
|---|---|---|---|---|---|---|
Name |
Mandatory |
QA |
Algorithms |
Visualization |
Own company |
Other users |
Part number |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Part MFR cage code |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Description |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Material domain |
Yes |
Yes |
Yes |
Optional |
Complete |
Anonymized |
List price |
Yes |
Yes |
Yes |
Optional |
Complete |
Anonymized |
List price currency |
Yes |
Yes |
NA |
NA |
NA |
NA |
Aircraft type |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Motor type |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
ATA chapter |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Back-to-birth-certification |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Contains kerosine |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Hazard item |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Maximum flight time |
No |
Yes |
Yes |
Optional |
Complete |
Anonymized |
Maximum cycles |
No |
Yes |
Yes |
Optional |
Optional |
Anonymized |
Maximum shelf life |
No |
Yes |
Yes |
Optional |
Optional |
Anonymized |
#6 - Interchangeabilities & Modification Information
The API documentation can be found here API DOC Interchangeabilities & Modification Information
The specification of the expected data formats and data types for CSV contributions is also documented on API documentation under Schemas -> Interchangeabilities & Modification Information
Data Field |
Utilization |
Visibility |
||||
|---|---|---|---|---|---|---|
Name |
Mandatory |
QA |
Algorithms |
Visualization |
Own company |
Other users |
Origin part number |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Origin part MFR cage code |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Alternative part number |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Alternative part MFR cage code |
Yes |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Modification necessary |
No |
Yes |
Yes |
Yes |
Complete |
Anonymized |
Modification price |
No |
Yes |
Yes |
Optional |
Optional |
Anonymized |
Modification price currency |
No |
Yes |
NA |
NA |
NA |
NA |