Heavy Maintenance Work Scope Loader provides the possibility of loading a customer work list, matching these tasks with existing items in the task library, creating new Event Codes for repeat events or one off activities and assignment of these events to a Maintenance Order to allow for further planning and scheduling. The process also supports numerous error and warning checks to ensure minimum user action during the assignment activity.
Maintenance Order needs to be Created, in one of the following states ‘Initial Scope Definition’, ‘Under Preparation’, ‘Released’ or ‘Started’
Top Part Number as assigned to the Maintenance Order must have a relation to an active Maintenance Program. Maintenance Program is set in Manage Serial Structure.
Work Scope file need to be in CSV format, when standard template is used "Semicolon" (";") need to be used a s delimiter for CSV file. CSV file should be created according to the structure below,
| Column Header | Uasge |
| Customer Mx Event Code | This column represents either an MPD Item Number, AD/SB reference or other Source code as provided from the Operator to the Service Provider, and is often referred to as Task Code. This will be used as Maintenance Code or Manual Maintenance Event Code. Length of this value is validated during the Work Scope Loading. |
| Customer Mx Event Code Description | This is the description of the Task Code, this will be used as Maintenance Code Description or Manual Maintenance Event Code Description. Length of this value will be validated during the Work Scope Loading. When length of this value exceeds the allowed 2000 characters, only the first 200 characters will be used as Event Code Description/Manual Maintenance Event Description. Full text is inserted into the ‘Remark’ attribute as associated with the Event Code |
| Customer Part Number | This is not a mandatory value and can be left blank. During the load the associated Top Part Number of the selected maintenance order will be used. |
| Customer Part Description | This is not a mandatory value, level this blank. During the load the associated Description of the Top Part Number in selected maintenance order will be used |
| Customer Serial Number | This is not a mandatory value, level this blank. During the load the associated Serial Number of the selected maintenance order will be used |
| Child Part Number | This column represents any Child Part Number which may require Time-Life Component inspections or replacements.
This should left blank for frequent events/MPD Items (when Single Visit is FALSE). For Manual Maintenance Events value specified here will be added as Remark. |
| Child Part Description | This column represents the description of the Child Part Number which may require Time-Life Component inspections or replacements.
This should left bank for frequent events/MPD Items ( when Single Visit is FALSE). For Manual Maintenance Events value specified here will be added as Remark. |
| Child Serial Number | This column represents the Serial Number of the Child Part Number which may require Time-Life Component inspections or replacements.
This should left bank for frequent events/MPD Items (when Single Visit is FALSE). For Manual Maintenance Events value specified here will be added as Remark. |
| Position | This column represents the position/location in the asset where the activity needs to be accomplished as related to the Child Part Number which may require Time-Life Component inspections or replacements (LH, RH, Cabin etc).
This should left bank for frequent events/MPD Items ( when Single Visit is FALSE). For Manual Maintenance Events value specified here will be added as Remark. |
| Single Visit/Use | This column indicates whether the Task Code should be handled as future recall, i.e. added to the library for future use or as a single occurrence.
For MPD Items/Frequent Events this value should be specified as 'FALSE'. For Single Events this need to be specified as 'TRUE'. |
| Contract Group | This column will indicate the Contract Group as associated to the Task Code. When creating an event this value will be used as a Contract Group of your event. During the Work Scope Load value specified here will be validated against the Heavy Maintenance Contract connected to the Maintenance Order. |
| Customer Origin Event Ref No | This will reflect the customer event task number associated with customer mx event code. Value specified here will be added as Remark. |
Load Work Scope command in Heavy Maintenance Work Scope Loader can be used to load the work scope file. This command will open a Load Work Scope assistancewhere the applicable Maintenance Order for the work scope needs to be retrieved. Once the Maintenance Order is selected then the source file is uploaded either by browsing to the storage location or by dragging and dropping the file into the page. Once the work scope file is selected a Load button is enabled for further processing and loading the scope against the Maintenance Order.
When the customer work scope is changed, it is possible to reload the updated work scope again and again until it is finalized. During the reload it is important to reload the full file, that will allow the system to identify any work scope items get deleted between two loads.
The following table shows a description of each status on Work Scope Items.
| Status | Description |
| Loaded | When Work Scope Items get uploaded via Work Scope file, Work Scope Item will set as Loaded. |
| Connected | When an Event is assigned to the Maintenance Order, such Work Scope Items will be set as Connected. |
| Removed | When already Connected Work Scope Item/s get deleted between scope loads, such items will be automatically set to Removed state. |
| Excluded | It is also possible for a user to mark events to be considered as ‘Exclude’ via the Exclude Mx Event command. Such items will be set to Excluded state. Work Scope Items in Excluded state will be excluded via the Process Work Scope Load function. |
When the Work Scope Items have been loaded, the Summary tab in Heavy Maintenance Work Scope Loader highlights relevant information in a summary format
This process will read the various attributes as set against the loaded events and either create:
| Future Recall Events (Frequently repeated events), set where Single Use = ‘FALSE’ |
|
| Single Use, set where Single Use = ‘TRUE’ |
|
Assign the created events to the Maintenance Order.
When Work Scope Items get removed between loads (work scope items in Removed status) will be listed in Removed Items tab,
During Process Work Scope Load if the user picked the option to Cancel Events connected to removed work scope items then those events will be automatically Cancelled. Cancelled Event flag will set as true for those Customer Mx Event codes.
Task Cards connected to all Customer Mx Event Codes can be seen in the Task Cards tab. When you want to see Task Cards connected to your Customer Mx Event Code you can either filter them in Task Card tab or you can see them in the nested table under each Customer Mx Event Code.
When a Task Card is connected to your Event, it will be automatically visualised in Heavy Maintenance Work Scope Loader page. Refresh of the page may be required in order to collect the related information.
The Maintenance Order button supports direct navigation to the relevant maintenance Order from the Heavy Maintenance Work Scope Loader page.
Snapshot command in Heavy Maintenance Work Scope Loader page can be used to navigate to Maintenance Order Snapshots page to see all connected snapshots. This command will be enabled only when you have snapshots connected to your Maintenance Order.