Importing Files

In an instance of IFS Cloud, a member of the deployed crew or an administrator uses the Disconnected Operations Workflow Manager to navigate to the location where the exported file is saved, upload the file, select what to import, and import the selected files. The same process is used by any FOB, MOB, or Technical Records Repository instance that is importing files.

During import, the system decrypts the file, verifies signatures, and extracts the file. The contents of the imported file are extracted with separate folders for aircraft, inventory shipments, technical records, and baseline updates. Note that when importing assets, the baseline and technical records files are hidden from view.
During import, the file categories are processed in the following order:

1. Baseline data for selected aircraft and shipments
2. Aircraft
3. Shipments of loose inventory
4. Technical records for selected aircraft and shipments

The data in the import file is treated as the source of truth if there are differences between the data in the import file and the data in the import location system.

When assets are imported successfully, the following changes occur in the destination instance of IFS Cloud:

• Asset records are created in the system and unlocked.
• If an asset previously existed in the system, it is unarchived, unlocked, and updated.
• The asset location changes to the default destination. Note that the status of the inventory does not change as a result of the transfer; and importing inventory to the DOCK location does not trigger the 'Force Inspection on Receipt' logic for items that have this flag enabled.
• Baseline synchronization runs on the assets.
• If a completed task or fault in the imported file already exists at the import location as an open task, then the status of the task or fault at the import location changes to CANCEL (Cancelled) with a Reason of REPLACED (Replaced By Import). If an imported task is complete in the import file and at the import location, it is ignored.
• If an exact duplicate of a technical record already exists in the destination system, the import ignores the record because no updates are required.
• If a duplicate of a technical record already exists in the destination system, but the records are not an exact match, the source record takes precedence and the destination record is updated.
• If a task definition exists in the system and a later revision of the same definition is imported, the existing revision status changes to SURPSEDE and the ACTV revision is now the imported one.
• Batch inventory is given a new batch number.
• The configuration information for sub-assemblies is updated in Maintenix if there is a conflict with the information in the imported file. (Inventory will be detached or attached).