Creating a visit package for unscheduled maintenance
In this page, you can create and confirm the visit package information. Tell me more
Select the “Create Visit Package” link under the “Visit Package” business component.
The “Create Visit Package” page appears.
The system displays the following field:
Date & Time Format |
The format in which the date and time fields are displayed. This format is displayed from the "User Preferences" business component based on the login user ID. In case the format is not defined, the system displays the date and time format from the “Enterprise Modeling” business component by default. |
The system displays the following field in the “Visit Package Details” group box, on clicking the “Create Visit Package” pushbutton:
Visit Package # |
A unique number generated by the system, to identify each visit package. The number, generated based on the “Numbering Type” selected, will be unique across aircraft. |
Enter the following:
Numbering Type |
Use the drop-down list box to select the numbering type, using which the visit package number will be generated by the system. Mandatory. The system lists the values defined for the “Visit Package” transaction in the “Create Numbering Class“ activity of the “Document Numbering Class” business component. |
Title |
The textual description of the visit package (Alphanumeric, 150). Mandatory. Zoom facility available. |
Aircraft Reg # |
The number identifying the aircraft for which the visit package is applicable (Alphanumeric, 30). Mandatory. The aircraft registration number should have already been defined in the “Create Aircraft Information” activity of the “Aircraft” business component and should be in “Active” status. Help facility available. |
The system displays the following field on clicking the “Create Visit Package” pushbutton:
Status |
The status of the visit package. The system displays one of the following: |
Fresh – when the visit package is created. | |
Confirm - when the visit package is confirmed. |
Enter the following:
CoM Required |
Use the drop-down list box to indicate whether the Certificate of Maintenance (CoM) must be issued after the maintenance activity is performed, in order to close the Visit Package. The system provides the options “Yes” and “No”, and sets the field to “Yes” by default. |
User Status |
Use the drop-down list box to assign a user-defined status for the visit package. The system lists all the “active” quick codes that are of type "User Status", as defined in the “Create Quick Codes” activity. Leave this field blank, if you do not wish to assign the user-defined status to the visit package. The system leaves the field blank by default. |
Project Code |
A unique code associated to the visit package, for tracking the execution of visit package (Alphanumeric, 30). |
Project File # |
The number identifying the project file of the visit package (Alphanumeric, 30). Help facility available. |
Project Time Unit |
Use the drop-down list box to select the time unit for the project. The system provides the options “Minutes”, “Hours” and “Days”. The system leaves the field blank by default. |
Visit Group |
Use the drop-down list box to specify the group to which the visit package belongs. The system lists all the “active” quick codes that are of type "Visit Group", as defined in the “Create Quick Codes” activity. Do not leave the field blank. |
The system displays the following field:
Approval Status |
Indicates the approval status of the visit package document. If the “Visit Package Approval” field is set to “Yes” in the “Set Options” activity, the system displays “Pending Approval”; else the system displays “Not Required”. |
Enter the following:
Visit Category |
Use the drop-down list box to specify the category to which the visit package belongs. Mandatory. The system lists all the “active” quick codes that are of type "Visit Category", as defined in the “Create Visit Category” activity of the “Central Planning” business component. |
Priority |
Use the drop-down list box to specify the priority or the level of urgency of the visit package. The system lists all the priority descriptions, which are in the “Active” status, as defined in the “Create Priority Numbers” activity of the “Common Master” business component. |
Maintenance Event |
Use the drop-down list box to select the maintenance event that must be considered as a part of the visit package. The system lists all the maintenance events defined in the “Maintain Maintenance Events” activity of the “Common Master” business component. Leave the field blank if you do not wish to specify any maintenance event. The system leaves the field blank by default. |
Expense Type |
Use the drop-down list box to specify the expense type for the visit package. The system lists the following options:
The system displays “Revenue” by default.. |
CAPEX Proposal # |
The capital expense proposal number applicable to the visit package. (Alphanumeric, 40). Ensure that the value entered here is a valid capital expense proposal number as defined in the “Asset Planning” business component, if the current business component interacts with the “Asset Planning” business component. Leave this field blank, if the expense type is “Revenue”. Help facility available. |
Note: The CAPEX Proposal number specified in the visit package must have an asset class that is same as the asset class to which the Asset Tag and Asset No. are mapped for the aircraft. The system performs this check only when the expense type is “Capital” and the “Enforce Object to Asset Mapping For” field is set as “Aircraft” in the “Set Option” activity of the “Account Group” business component.
To copy visit package details
Enter the following in the “Copy Details” group box:
Visit Package # |
The number identifying the visit package, the details of which are to be copied into the visit package that is currently being defined (Alphanumeric, 18). The visit package should have already been defined in the “Create Visit Package” activity, and must be in “Released” or “Closed” status. The visit package should be applicable for this execution center. Data entry in this field is mandatory, if you wish to copy the visit package details to the visit package currently being defined. |
|
Check one or more of the following boxes, to specify the details of the visit package to be copied.
All Tasks |
Check this box to copy all the work units and component removal details of the visit package. |
Aircraft Tasks |
Check this box to copy the work units that are of job type “Aircraft”. |
On-Wing Tasks |
Check this box to copy the work units that are of job type “On-Wing”. |
Component Removal List |
Check this box to copy the work units that are of job type “Component Removal”. |
Note:The system copies the restoration work units from the “Component Maintenance Program” business component. |
|
Non-Routine Tasks |
Check this box to copy the work units, which have a reference to the maintenance report. |
Eng. Doc Tasks |
Check this box to copy the work units, which have a reference to the Engineering Order (EO) . |
Click the “Get” pushbutton to copy the visit package details.
Note: If 'All Tasks' option alone is checked, then the system copies all the details of the visit package # present in the Copy Details field into the new visit package including Expense Type and Capex Proposal # of the corresponding work units from the work unit details.
If 'Aircraft Tasks' option alone is checked, then the system copies all the work units which have Job Type defined as 'Aircraft Related' for the visit package # present in the copy details field into the new visit package including Expense type and Capex Proposal # defined for the work units into the new work unit details.
If 'On Wing Tasks' option is checked, then the system copies all the work units which have Job Type defined as 'On Wing' for the visit package # present in the copy details field into the new visit package including Expense type and Capex Proposal # defined for the work units into the new work unit details.
If 'Component Removal Tasks' option alone is checked, then the system copies all the work units which have Job type defined as 'Component Removal' for the visit package # present in the copy details field into the new visit packageincluding Expense type and Capex Proposal # defined for the work units into the new work unit details.
If 'Non-Routine Tasks' option alone is checked, then the system copies all the work units which have a DMR # reference for the visit package # present in the copy details field into the new visit package.
If 'Eng Doc.- Tasks' option alone is checked, then the system copies all the work units which have a Eng Doc # reference for the visit package # present in the copy details into the new visit package.
If multiple check boxes are selected then the system will copy the combination as per the above description. The schedule dates of the copied work units should be adjusted as per the planned start date of the new visit package. If the planned start date is left blank, then the system assumes the grounding date as the planned start date.
Customer details
The system displays the following in the “Customer Details” group box:
Customer # |
The number identifying the customer, who owns the aircraft. | ||||||
Customer Name |
The name of the customer owning the aircraft. | ||||||
Note: The "Customer #" and "Customer Name" fields are applicable only when the aircraft is not self-owned and the customer details are recorded in the system.
Note: If a value is entered in the “Customer Order #” field and if the current business component interacts with the “Customer Order” component, then ensure that:
The system displays the following:
|
To specify the execution details
Enter the following in the “Execution Details” group box:
Grounding Date |
The date on which the aircraft will be grounded for the execution of maintenance activities (Date Format). Mandatory. |
The system displays the following field:
Projected End Date |
The date on which the visit package execution must be completed. The system displays the latest date of the scheduled end dates of the work units displayed in the multiline. |
Enter the following:
Planned Start Date |
The date on which the visit package execution must be started (Date Format). The date entered in this field cannot be earlier than the “Grounding Date”. |
Note: If you leave this field blank, the system sets the grounding date as the planned start date, on clicking the “Create Visit Package” pushbutton.
Planned End Date |
The date by which the visit package execution should be completed (Date Format). The date entered here must be later than the date entered in the “Planned Start Date” field. If you leave this field blank, the system displays the latest date of the planned end dates specified for the work units in the multiline |
Est. Elapsed Time |
The total time estimated for completing the visit package (Decimal). Use the drop-down list box provided alongside, to specify the unit of measurement for the time allotted for the visit package. The system displays the options “Minutes”, “Hours” and “Days”, and sets the field to “Hours” by default. |
Note: The system calculates the estimated elapsed time as follows:
If the “Planned End Date” is specified, the difference between the plan start date and plan end date is displayed. Otherwise, the maximum elapsed time specified in the multiline for the work units, is displayed.
Est. Man Hrs. |
The total man-hours estimated for “skill” type resources to complete the visit package (Decimal). The number entered in this field must be positive. The system sets the field to the estimated man-hours, or the sum total of the estimated man-hours entered in the multiline, whichever is greater. |
Primary Work Center # |
Use the drop-down list box to select the work center to which the visit package is allotted. Mandatory. This work center acts as primary responsibility center. The system lists all the “Active” work centers associated to the current organization unit to which the login user has access. |
The system displays the following field on clicking the “Create Visit Package” pushbutton:
Primary Work Center Desc |
The textual description of the work center. Zoom facility available. |
Enter the following:
Visit Planner |
The code identifying the employee who plans the visit package (Alphanumeric, 15). Mandatory. The employee code should have already been defined in the “Employee Information” business component and should be in “Active” status. The system displays the employee code of the logged in user by default. Help facility available. |
The system displays the following field on clicking the “Create Visit Package” pushbutton:
Planner Name |
The name of the employee, who plans the visit package. |
To record the work unit details
Enter the following in the “Work Unit Details” multiline:
Seq # |
The sequence in which the work unit should be performed, while executing the visit package (Integer). Ensure that the sequence number is a positive integer and is unique in the multiline. If you leave the sequence number blank, the system automatically assigns a sequence number to each row, in the order in which they are entered in the multiline, on clicking the “Create Visit Package” pushbutton. Ensure that you do not leave the field blank for any of the work units occurring in between. |
Work Unit # |
The number identifying the task that must be performed while executing the visit package (Alphanumeric, 30). Mandatory. The task number should have already been defined in the “Create Task” activity of “Maintenance Task” business component and must be in “Active” status. Help facility available. |
Work Unit Type |
Use the drop-down list box to select the type of the work unit .The combo is loaded with the value “Task”. |
Note: While confirming the visit package, the system ensures that the work unit and the work unit type combination is valid for the aircraft specified in the “Aircraft Reg #” field for the job type selected as “Aircraft”.
The work unit is also checked against the component in the “Component #” field for the on-wing and component replacement jobs.
For the work unit of type “Task”, the related tasks are identified recursively and retrieved along with their corresponding material and resource requirements, from the “Maintenance Task” business component.
The system displays the following field on clicking the “Create Visit Package” pushbutton:
ATA # |
The ATA chapter associated to the part #, serial # or Component ID of the selected aircraft reg # as defined in the “Configuration” business component. If ATA # information is not available for the particular part, then the system retrieves the information from the NHA of that part. |
Enter the following:
Work Center # |
The work center where the work unit must be performed (Alphanumeric, 30). Mandatory. The system ensures the following: |
If the “Work Center Hierarchy Check” field is set to “Yes” in the “Set Options” activity, the work center should be either primary work center or child work center associated to the primary work center entered in the “Primary Work Center #” field. Otherwise, the work center specified here must be associated to the organization unit. | |
Help facility available. | |
Note: For the newly added work units in the multiline, if the “Work Center” field is left blank, the system retrieves the work center identified for the task in the “Maintenance Task” business component. If no valid work center is identified for the task, the system retrieves the primary work center of the visit package. |
|
Part # |
The part number of the component on which the work unit must be performed (Alphanumeric, 40). The part number must have been defined in the “Create Parts Main Information” activity of the “Part Administration” business component, and must be in “Active” status. The part must have a valid component ID defined in the “Aircraft” business component. Help facility available. |
Serial # |
The serial number of the component on which the work unit must be performed (Alphanumeric, 40). Ensure that the serial number entered is an active serial number available in the “Stock Maintenance” business component, and is valid for the part. Help facility available. |
Data entry in this field is mandatory, if the position code entered in the “Position Code” field is not unique for the aircraft configuration. | |
Position Code |
The position code to which the component is fitted (Alphanumeric, 25). The position code must have already been defined for the aircraft entered in the “Aircraft Reg #” field, in the “Maintain Aircraft Configuration” activity of “Configuration” business component, and must be in “Active” status. Ensure that no component is attached to this position code, if the replacement type is set to “Attach Only”. Help facility available. |
If the position code is unique for the aircraft configuration, the system retrieves the part number, serial number and component ID fitted in the position code. |
Note: If you leave this field blank, the system retrieves the position code for the part number and serial number (if entered) combination or for the component ID (if entered).
Ensure that no component is attached to the position code specified here, if the replacement type is set to “Attach Only”.
Note: If the engagement type of the aircraft is “Full Maintenance”, then ensure the following:
The "Position Code" field is not left blank for the on-wing jobs.
The position code is in “Active” status for those parts for which no restoration work units are identified, and replacement type is other than “Remove Only”.
Maintenance Type |
Use the drop-down list box to select the type of the maintenance to be performed on the component. The system provides the following options: “Overhaul”, “Repair”, “Inspection” and “Others”. Leave this field blank, if you do not wish to specify the maintenance type. You must compulsorily select a maintenance type, if the “Part #”, “Serial #”, “Component #” or “Position Code” is entered, and if the “Job Type” is set to “On-Wing”. |
Component # |
The component ID on which the work unit must be performed (Alphanumeric, 90). The component ID must have been defined in the “Create Component Record” activity of the “Aircraft” business component, and must be in “Active” status. Data entry in this field is mandatory, if the “Job Type” field is set to “On-Wing” and if the position code entered in the “Position Code” field is not unique for the aircraft configuration. Data entry in this field is mandatory, if the engagement type of the aircraft is “Full Maintenance” and there exists more than one level code for the position code entered. Help facility available. |
If the “Job Type” field is set to “Aircraft”, the “Part #”, “Serial #”, “Position Code”,and “Component #” fields must be left blank.
If the “Job Type” is set to “On-Wing”, the component ID or the base part number of the part must have been defined as the component effectivity for the work unit in the “Maintenance Task” business component.
If the “Job Type” is selected as “Aircraft”, the system checks for the aircraft effectivity of the work unit in the “Maintenance Task” business component.
The system ensures that the part and serial number or the component ID is attached to the aircraft, while confirming the visit package.
To record work unit execution details
Time Unit |
Use the drop-down list box to specify the unit of measurement for the time allotted for the work unit. The system displays the options “Minutes”, “Hours” and “Days”, and sets the field to “Hours” by default. |
Est. Elapsed Time |
The time estimated for completing the work units (Decimal). The number entered in this field must be positive. If you leave this field blank, the system displays the estimated elapsed time entered for the work unit in the “Maintenance Task” business component. |
Est .Man Hrs. |
The total man-hours estimated for completing the work unit (Decimal). The number entered in this field must be positive. If you leave this field blank, the system displays the estimated man-hours entered for the work unit in the “Maintenance Task” business component. |
Sch. Start Date |
The date on which the work unit execution must start (Date Format). The date entered in this field must be later than the “Planned Start Date”. |
Note: If you leave this field blank, the system sets the planned start date as the schedule start date.
Start Time |
The time at which the work unit execution must be started (Time Format). If you leave this field blank, the system defaults the start date defined for the work center. |
Sch. End Date |
The date on which the work unit must be completed (Date Format). The date entered in this field should be earlier than the “Planned End Date”. |
If you leave this field blank, the system displays the sum of the schedule start date and the “Est. Elapsed Time” (converted in days, based on the conversion factor defined in the “Common Masters” business component). If the “Sch. End Date” and “End Time” fields are left blank, and if the “Time Management Scheduling” business component exists in the login organizational unit, the system calculates the end date and time from the time management definitions and the employee calendar. Otherwise, the system calculates the end date and time based on the start date and the estimated time | |
End Time |
The time at which the work unit must be completed (Time Format). |
Note: If the “Sch Start Date” and “Sch End Date” fields are same, the “End Time” must be greater than the “Start Time”.
Priority |
Use the drop-down list box to specify the priority with which the work unit must be executed. This priority will be used in the “Hangar Work Order” business component. The system lists all the priority descriptions that are in the “Active” status, as defined in the “Create Priority Numbers” activity of the “Common Master” business component. |
Job Type |
Use the drop-down list box to select the job type, which could be “Aircraft”, “On-Wing” or "Component Removal". Mandatory. The system sets the field to “Aircraft” by default. |
Note: If the “Component Removal” option is selected, ensure that restoration work units are defined for component removals.
The system displays the following on clicking the “Create Visit Package” pushbutton:
Note:1. The system retrieves all the related tasks with the Parents Tasks in the “Parent Task #” column and the relationship between the Task # and Parent Task # in the Relationship Type” column.
2. All the attributes of the parent tasks will get copied to related tasks.
Parent Task # |
The code identifying the parent task of the work unit. |
Relationship Type |
The relationship type of the task with the work unit. |
Change Doc Type |
The type of the change document, which could be “EO” or “FCD”. |
Change Order # |
The number identifying the engineering order or the fleet campaign directive. |
Work Center Description |
The textual description of the work center. |
Work Unit Desc |
The textual description of the work unit. |
Zone # |
The zone number associated to the position code or component ID. |
Enter the following fields in the “Work Unit Details” multiline:
Expense Type |
Use the drop-down list box to specify the expense type for the visit package. The system lists the following options:
By default the system leaves the field blank. If this field is left blank, then the expense type set in the header gets defaulted here. |
Note: Ensure that the expense type is set as “Revenue” for each row in the multiline, if the expense type is set as “Revenue” in the header.
Note: Ensure that at least one work unit in the multiline is of expense type “Capital”, if the expense type is set as "Capital" in the header.
CAPEX Proposal # |
The capital expense proposal number applicable to the work unit (Alphanumeric, 40). Ensure that the value entered here is a valid capital expense proposal number as defined in the “Asset Planning” business component, if the current business component interacts with the “Asset Planning” business component. Leave this field blank, if the expense type is “Revenue”. Help facility available. |
Note: The CAPEX Proposal number specified against the work unit must have an asset class that is same as the asset class to which the Asset Tag and Asset No. are mapped for the aircraft. The system performs this check only when the expense type is “Capital” and the “Enforce Object to Asset Mapping For” field is set as “Aircraft” in the “Set Option” activity of the “Account Group” business component.
Check the box in the multiline and click the Delete icon provided in the tool bar above the multiline to delete the work unit from being included in the visit package.
Enter the following:
Comments |
Any remarks or comments pertaining to the visit package (Alphanumeric, 255). Typically any additional information about the visit package can be entered here. Zoom facility available. |
Note: You have to ensure that atleast one work unit is entered while confirming the visit package.
If
you wish to insert work units in the multiline and assign sequence number
for them, click the “Re-Number” pushbutton to rearrange the existing rows
in the ascending order of the sequence number. The system regenerates
the sequence number in multiples of five, thereby enabling you to specify
the sequence number for the newly added work units.
Create visit package
Click the “Create Visit Package” pushbutton, to create the visit package.
The system performs the following:
Generates the visit package number and sets the status of the created visit package to “Fresh”.
Updates the work unit details and the planned dates of the visit package. All the part requirements, resource requirements, the access panel relationships and the task relationships for the work units are also copied to the visit package.
Parts which are defined as Non-Stockable in the interacting Part Administration business component are not copied.
For the newly added work units in the multiline, all the part and resource requirements identified for the task are retrieved from the “Maintenance Task” business component.
Updates the newly added work units as unplanned work units in the “Customer Order” business component, if the customer order number is specified and if the current business component interacts with the “Customer Order” business component
For all the parts with part type set as “PBH”, the system updates the stock status to “PBH” only if the following conditions are satisfied.
a) The part is identified as PBH part for the supplier who is mapped to the aircraft specified in the “Aircraft Reg #” field.
b) The part and its higher assembly part are identified as PBH object list for a supplier.
c) The component that is requested for a “Component Removal” job or “Onwing” job, along with its higher assemblies, is identified as PBH for the supplier.
For the work center entered in the multiline, the system checks for the work center–part type–issue warehouse mapping, in the “Work Center” business component.
For customer-owned aircraft, the system retrieves the stock status for each part from the “Customer Order” business component, if a valid customer order is specified, and if the current business component interacts with the “Customer Order” business component.
For owned aircraft, the system updates the stock status of each part as the preferred stock status of the aircraft, specified in the “Aircraft” business component.
Ensures that the aircraft registration number for which the visit package is created, is mapped to the asset ID and the asset tag in the “Maintain Asset Tracker” business component, if the expense type is set as “Capital’ and if the “Enforce Object to Asset Mapping For” is set as “Aircraft” in the “Set Options” activity of the “Account Group” business component.
If the Visit Package is created with reference to a valid customer order and if the “Approval of Additional Work Scope” is set to “Required” or “As Required” in the “Customer Order” business component, the system
sets the “Approval Status” of the newly added work units to “Pending Cust. Auth.", if the “Visit Package Approval” is set to “No” in the “Set Options” activity of the current business component.
sets the "Approval status" of the work unit to "Pending Approval”, if the “Visit Package Approval” is set to “Yes”.
If the Visit Package is created with reference to a valid customer order and the if Approval of Additional Work Scope is set to "Not Required" in the “Customer Order” business component, the system
sets the "Approval Status" of the newly added work unit to "Pending Approval, if the “Visit Package Approval” is set as "Yes".
sets the "Approval Status" of all the work units to "Not Required", if the “Visit Package Approval” is set as "No".
The system ensures the following for confirming the visit package:
The part number should have the planning information specified in the “Part Administration” business component.
Click the “Confirm” pushbutton, to confirm the visit package details.
The system performs the following on confirming the visit package:
Sets the status to “Confirmed”.
Generates a plan entry for the dispositionable parts requirements in the “Stock Planning” business component.
The system retrieves the access panels defined for the work units entered in the multiline. The system retrieves the open and close access panel tasks associated to the access panels.
Each open access panel task is associated to the task, which first requires the access panel to be opened. Each close access panel task associated to the task, which lastly requires the access panel to be closed.
The task to which the open and close access panel task is associated, is called the parent task. The schedule date and time of the open access panel task is set to the schedule start date and time of the parent task. The schedule date and time of the close access panel task is set to the schedule end date and time of the parent task.
The status of the access panel tasks that are included in the visit package is set as “Pending Opening”.
For the newly added work units in the multiline, all the part and resource requirements identified for the task are retrieved from the “Maintenance Task” business component.
Updates the newly added work units as unplanned work units in the “Customer Order” business component, if the customer order number is specified and if the current business component interacts with the “Customer Order” business component.
For all the parts with part type set as “PBH”, the system updates the stock status to “PBH” only if the following conditions are satisfied.
a) The part is identified as PBH part for the supplier who is mapped to the aircraft specified in the “Aircraft Reg #” field.
b) The part and its higher assembly part are identified as PBH object list for a supplier.
c) The component that is requested for a “Component Removal” job or “Onwing” job, along with its higher assemblies, is identified as PBH for the supplier.
For all the other part types, the system updates the stock status as “Accepted”.
For the work center entered in the multiline, the system checks for the work center–part type–issue warehouse mapping, in the “Work Center” business component.
For customer-owned aircraft, the system retrieves the stock status for each part from the “Customer Order” business component, if a valid customer order is specified, and if the current business component interacts with the “Customer Order” business component.
For owned aircraft, the system updates the stock status of each part as the preferred stock status of the aircraft, specified in the “Aircraft” business component.
The system ensures that all parts identified as spare part requirements have their planning and reference status as “Active”.
If the Visit Package is created with reference to a valid customer order and if the “Approval of Additional Work Scope” is set to “Required” or “As Required” in the “Customer Order” business component, the system
sets the “Approval Status” of the newly added work units as “Pending Cust. Auth.", if the “Visit Package Approval” is set to “No” in the “Set Options” activity of the current business component.
sets the "Approval Status" of the work unit as "Pending Approval”, if the “Visit Package Approval” is set to “Yes”.
If the Visit Package is created with reference to a valid customer order and the if Approval of Additional Work Scope is Set as "Not Required" in the “Customer Order” business component, the system
sets the "Approval status" of the newly added Work Unit as "Pending Approval, if the “Visit Package Approval” is set as "Yes".
sets the "Approval Status" of all the work units as "Not Required", if the “Visit Package Approval” is set as "No".
Check the box in the “Select” column of the multiline, to mark the work unit for which the resource and part requirement details must be entered.
To proceed, carry out the following
Select the “Edit Material Requirements” link at the bottom of the page, to enter the material required for executing the visit package.
Select the “Edit Resource Requirements” link at the bottom of the page, to enter the resource required for executing the visit package.
Select the “Process Deferred Discrepancies” link at the bottom of the page, to associate a deferred maintenance report to the visit package.
Select the “Perform Opportunity Maintenance” link at the bottom of the page, select the work units for opportunity check and assign for the visit package.
Select the “Plan Visit Package” link at the bottom of the page to schedule import and export of work units included in the visit package to the project management software.
Select the “Edit Work Content” link at the bottom of the page, to modify the work unit details.
Select the “Update Component Removal List” link at the bottom of the page to specify the component restoration details.
Select the “Edit Visit Package Details” link at the bottom of the page to modify the visit package details.
Select the “Edit Visit Level Material Reqmts” link at the bottom of the page to specify the material required for executing the visit package.
Select the “Edit Visit Level Resource Reqmts” link at the bottom of the page to specify the resource required for executing the visit package.
Select the “View File” link at the bottom of the page to view the project file contents.
Select the “View Error Log” link to view the details of errors generated during confirmation or release of the visit package.
Choose a numbering pattern to generate visit package number
Indicate whether COM is required or not
Copy details from an existing visit package
Confirm the visit package details
Choose a numbering pattern to generate visit package number
You can select a numbering type for the visit package. A unique visit package number will be generated by the system based on the numbering type selected.
Select the numbering type in the “Numbering Type” drop-down list box.
Enter all other visit package details.
On clicking the “Create Visit Package” pushbutton, the system generates the visit package number using the selected numbering type.
Indicate whether COM is required or not
You can specify whether the Certificate of Maintenance must be issued for the aircraft after completion of the maintenance activity.
Set the “CoM Required” field to “Yes”,to make it mandatory for the CoM to be issued after the visit package has been performed.
Set the “CoM Required” field to “No”, if you do not wish to issue the CoM.
Copy details from an existing visit package
You can copy details from a visit package that is already defined. Details such as the aircraft, on-wing, component removal, non-routine, engineering order or fleet campaign directive work units can be copied, along with the expense type and the capital expense proposal number defined for the work units.
Enter the number of the visit package from which details must be copied, in the “Copy Details” group box.
Check one or more of the boxes “All Tasks”, “Aircraft Tasks”, “On-Wing Tasks”, “Component Removal List”, “Non-Routine Tasks” or “EO/FCD Tasks”, to specify the details to be copied.
Click the “Get” pushbutton to copy the details.
The system copies the work units to the visit package.
4 “Create Numbering Class” activity under “Document Numbering Class” business component.
4 “Create Aircraft Information” activity under “Aircraft” business component.
4 “Create Task” activity under “Maintenance Task” business component.
4 “Create Work Center” activity under “Work Center” business component.
Creating a visit package for unscheduled maintenance – An overview
In this page, you can create and confirm the visit package information. A unique visit package number will be generated by the system, based on the numbering type that you select in this page.
You must enter the aircraft registration number for which the visit package is applicable, and specify whether the Certificate of Maintenance must be issued for the aircraft, after completion of the maintenance activity.
You can assign a user-defined status and priority for the visit package, enter the group and category to which the visit package belongs, and the project code, which helps in cost tracking.
You can also provide a reference to a visit package that is already defined and selectively copy details such as the aircraft task, on-wing task, component removal list, non-routine tasks, and engineering order and fleet campaign directive tasks.
The following details can be recorded for the execution of the visit package:
the date on which the aircraft will be grounded for visit package execution
the planned start date and end date for visit package completion
the estimated time and man-hours to complete the visit package
the work center where the maintenance activity is performed
the employee who is planning the visit package.
You can enter the work units that must be performed as part of the maintenance activity and specify the sequence in which they have to be carried out, while executing the visit package. The work center where the work unit must be performed, the part number, serial number and the component ID on which the work unit must be performed, and the type of maintenance can be specified. You can indicate the time and man-hours estimated to complete the work unit, the start date and end date for work unit completion and assign a priority for the work unit.
The system generates the visit package number, updates the details, and sets the status of the visit package as “Fresh”.
You are also provided with the option of confirming the visit package in this page. On confirmation, the system sets the status of the visit package to “Confirmed”.