Overview

Workpacks created in CAMP can be imported into Tech Log for viewing or signing off. In order for a workpack to show in Tech Log, there are two requirements:

• The Importing Workpacks function must be enabled for the aircraft. Please Contact Support if you are unsure about this.
• Within the CAMP User Interface, the Post to external system checkbox must be checked against the specific workpack. There is no ability for Tech Log to see the workpack until this has been checked:

At the next sync (automatic or manual), the workpack will be brought into the Tech Log Web Dashboard in the Draft status. 

Workpack Items

Items contained within a workpack imported from CAMP will attempt to be matched against the Maintenance List of items previously imported via Importing Maintenance Items and Defects. These items are linked based on:

• Task Reference
• Task Description
• Status

While it is common to have multiple tasks with the same reference (e.g. those that are performed on each engine), within CAMP the component position is included in the description, and so matching based on both Reference and Description allows for the same task number to be imported against multiple components. Should two tasks have the same reference and description, CAMP does not provide any further way to differentiate between them and so only one copy of the task will be included within the Tech Log Web Dashboard.

The Maintenance Item's status is considered as it is possible, and indeed happens often, that a task be completed in Tech Log before it is closed down in CAMP. An item that has recently (within the past 14 days) been completed within Tech Log will be assumed to be the same task if it is seen in a new or updated Workpack from CAMP, allowing 14 days for any task's status to be updated within CAMP. Note that this additionally does impose the limit that a task with the same reference and description cannot be repeated within 14 days of the last iteration and included in a Workpack from CAMP.

If no Maintenance Item exists within Tech Log that matches the reference and description, and passes the status check, the item will be created as a placeholder for signing off. Unfortunately, CAMP does not provide full task details in this case, and so only the description and reference will show with no limit information. This can happen in situations where the duration ahead which we are able to pull tasks from the Due List is less than the forecast date of the task itself. Should the same task later appear in the Due List, we will correctly link it to the Workpack Item and display its limits. This is a limitation imposed on us by CAMP.

Imported Workpack Status

If your aircraft is not using the Review/Approval Flow (see below), all workpacks will be imported according to their status within CAMP: either Active or Complete.

If your aircraft is using the Review/Approval Flow, the Workpack will be imported as Active only if all of the items within the Workpack have been approved. If the Workpack contains any item that has not been approved, the status will be set to Draft. This ensures that the Workpack cannot be signed off until all items have been approved, see the next section for details.

Review/Approval Flow

If your aircraft is using the Review/Approval Flow (see TL-UGD-CMP-002 Importing Maintenance Items and Defects), Workpack Items that are not linked to an already approved Maintenance Item will need to be approved before they can be completed. This can be achieved either by using the Review/Approval Flow itself, or by editing the Workpack and turning the Status Toggle to the On position. At this point, if the Workpack contains Draft items, you will be asked to approve them:

Updating Workpacks

The requirement to check "Post to external system" within CAMP typically means that only finalised workpacks are imported into Tech Log. That said, Tech Log does support handling changes in CAMP workpacks after they have been imported.

It's important to note that workpacks are identified by their "Workorder Number" within CAMP. If this number is altered in any way, the workpack will be perceived as being new and imported as a separate workpack. The original workpack, using the old reference, will need to be manually deleted from Tech Log.

Mixed Source Workpacks

A workpack that originated from CAMP can have additional items added to it, providing that these items did not also originate from CAMP. Adding additional CAMP-originated items to a CAMP-originated workpack must be done from within CAMP.

It is, however, possible to create a new workpack with any combination of CAMP-originated and non-CAMP-originated items, providing that the workpack is first created within the Tech Log Web Dashboard.

In the former case, when a CAMP-originated Workpack has (non-CAMP-originated) items added to it in Tech Log, only the CAMP-originated items will be kept in sync with changes made to the Workpack in CAMP. This includes removing items or adding new ones. A Tech Log-originated workpack will never be synchronised with CAMP regardless of the items it contains.

Adding Items to a Previously Closed Workpack

If a Workpack has been closed (either by synchronising the closure within CAMP, or because a CRS has been issued for the Workpack within Tech Log), adding an item to the Workpack in CAMP will cause the Workpack to be re-opened in Tech Log. The Workpack would need to be signed off again in order to close out the new item.

Applying a CRS to a Workpack

Once a workpack has been marked as Active (i.e. the Status Toggle is set to On and the Workpack saved), it is available to be completed in the regular way. Unfortunately, CAMP does not have any mechanism that allows reporting back on the status of a workpack or the individual items, so while resolving the workpack in Tech Log will mark the items as resolved within our application, they must be manually marked as RTS, or closed down, within CAMP.