Depending on what you need to do, you prepare a full deployment or send an update.
Deployment option | Use to | Notes |
Full deployment |
|
A portion of the asset's technical records and baseline updates are automatically included in the exported file. |
Send update |
|
Creating and exporting a file is a two-step process of preparing the deployment and then exporting a ZIP file.
For steps, see topics below:
For more information, see Disconnected Operations
Note:
Loose inventory and pack-up kits are deployed in shipments, so a shipment containing a pack-up kit or loose inventory items must be created in Maintenix before it's available for you to deploy.
In full deployments, the system automatically includes a portion of the asset's technical and baseline batches in the export file, but these items are hidden from view. If the asset cannot be prepared for export, the asset's technical records and the baseline batch files are not prepared for export.
Tip: You can filter lists. For example, click the filter icon and enter the serial number in the serial filter field. If you have IFS Maintenix open in another browser tab you can copy a serial number or another filter value.
Result: The system starts to prepare the file and displays a unique Transfer ID for the file.
Result: On the Export File page you see the Transfer ID and status for the file.
Troubleshooting:
Transfer ID Status | What To Do |
Ready To Export but you want to cancel the transfer | If all the selected aircraft and shipments
have the Ready status, but you decide not to export the prepared file. Click Mark As Done. This changes the status of items in the nested to Cancel. Warning: You must now go to Maintenix and unarchive aircraft or inventory assets. |
Ready With Errors | One or more of the selected aircraft or
shipments is not included in the file. Click View Errors and try to resolve the errors. You can proceed to export a file in Ready With Errors status. If you export the file, the sub-files in Error status are not exported. To export these items, any associated errors must be resolved and then you can prepare a new deployment. |
Error | The file cannot be exported. Click the View Errors button and try to resolve the errors. |
Result: The export file is downloaded to your local machine. You can copy it to a file path, drop box, USB stick location where the destination location can access and import the file.
If the system has no record of the last batch sent to the destination,
then you send all baseline updates - up to the latest batch at your
location. If a base has communicated which batch they are currently on, you
can manually select the next batch in the sequence as the starting point for
the range of updates to send. If you select a batch, then the export
includes the batches starting from the one you select to the latest batch at
your location.
- If the current batch of the destination is unknown, select Send all updates.
- If the destination base has communicated the batch number they are currently using, select I want to select the starting batch number, then select the batch number.
Result: The system starts to prepare the file and displays a unique Transfer ID for the file.
Result: On the Export File page you see the Transfer ID and status for the file.
Result: The export file is downloaded to your local machine. You can copy it to a file path, drop box, USB stick location where the destination location can then access and import the file.
Note: The number of days worth of records that are transferred when you send an update is configured during initial set-up of IFS Cloud. You don't select a particular set of records here.
Result: The system starts to prepare the file and displays a unique Transfer ID for the file.
Result: On the Export File page you see the Transfer ID and status for the file.
Result: The export file is downloaded to your local machine. You can copy it to a file path, drop box, or USB stick location where the destination location can access and import the file.