Build Asset Structure Hierarchy
In this page, you can build the hierarchy for the selected asset structure. Tell me more
Select the “Build Hierarchy” link in the “Asset Structure Code Selection” page. Alternatively, select the hyperlinked asset structure in the multiline of the same page.
The “Build Asset Structure Hierarchy” page appears.
The system displays the following fields:
|
Asset Structure |
The asset structure for which you wish to build the hierarchy. Typically, this can be referred to as the “Apex Asset Structure”. The description of the asset structure is displayed alongside. Zoom facility available. |
|
Type |
The type of the asset structure, which can be “Rotables”, “Normal” or “Spares”. |
Enter the following field:
|
Parent Structure |
Use the drop-down list box to select the asset structure for which child asset structures must be defined. You can enter the child asset structures in the multiline. On clicking the “Next” pushbutton, the system fills this drop-down list box with the child asset structures entered in the multiline, sorted in the alphabetical order. The system leaves the field blank, when the page is launched the first time and retrieves in the multiline, the details of the apex asset structure that is displayed in the “Asset Structure” field. |
The system retrieves all the child asset structures belonging to the selected parent asset structure, in the “Children” multiline.
Enter the following field in the multiline, if you wish to attach new asset structures to the selected parent asset structure:
|
Child Structure |
The asset structure to be attached to the selected parent asset structure (Alphanumeric, 30). Ensure that the asset structure is already defined in the “Create Asset Structure Code” activity and is in the “Active” status. You cannot however modify this field when the page is launched for the first time as the details of the apex asset structure would be retrieved in this field. |
|
Press <Enter>. The system retrieves the “Type” and “Description” fields in the multiline. |
|
|
Include Child? |
Use the drop-down list box and select “Yes”, if you wish to include the child asset structures of the asset structure entered in the “Child Structure” field, in the hierarchy. If you do not wish to include the child asset structures in the hierarchy, select “No”. If you leave the field blank, the system considers it as “No”. |
The system displays the following field in the multiline:
|
Desc. |
The description of the asset structure. The system displays this field only on clicking the “Submit” pushbutton. |
|
Type |
The type of the asset structure, which can be “Rotable” or “Normal”. |
Enter the following fields in the multiline:
|
Spare Structure |
The spare structure to be attached to the asset structure (Alphanumeric, 30). Ensure that the spare structure is already defined in the “Create Asset Structure Code” activity and is in “Active” status. Help facility available. |
|
Item |
The item number of the rotable equipment that is to be created from the asset structure (Alphanumeric, 30). Data entry in this field is mandatory, if the “Type” field is “Rotable”. Leave the field blank, if the type of the asset structure is not “Rotable”. Help facility available. |
|
Variant |
The variant of the item (Alphanumeric, 5). Data entry in this field is mandatory, if variants have been defined for the item specified in the “Item” field. |
|
Remarks |
Any additional information about the asset structure (Alphanumeric, 150). |
Check the box in the “Select” column of the multiline, to mark the asset structure for deletion or to view additional details of the asset structure.
Click the Delete icon in the tool bar above the multiline.
Note: The system removes the selected asset structure from the hierarchy, and also releases all the child asset structures that are defined for it, from the hierarchy.
Click the “Submit” pushbutton, to attach the child asset structures to the parent asset structure.
Note: The system attaches the asset structures in the hierarchy, at a level next to the level of the parent asset structure selected in the “Parent Structure” drop-down list box. If you have set the “Include Child?” field as “Yes”, the system includes the child asset structures, if any, that are already defined for the asset structure in the multiline in the hierarchy.
Click the “Next” pushbutton, to fill the “Parent Structure” drop-down list box with the asset structures that are displayed in the multiline. Also, the system automatically lists the child asset structures of the first asset structure in the drop-down list box, in the multiline.
The system fills the “Parent Structure” drop-down list box with all the child asset structures in the multiline. The asset structures are listed in the alphabetical order and the first asset structure is displayed by default. The child asset structures belonging to this default asset structure are retrieved in the multiline.
Click the “Previous” pushbutton, to fill the “Parent Structure” drop-down list box with the asset structures that are in the previous level. Also, the system automatically lists the child asset structures of the first asset structure in the drop-down list box, in the multiline.
The system fills the “Parent Structure” drop-down list box with the asset structures defined at the previous level in the hierarchy. The asset structures are displayed in the alphabetical order and the first asset structure is displayed by default. The child asset structures belonging to this default location are retrieved in the multiline.
To proceed, carry out the following
Select the “View Attached Parameters” link from the bottom of the page, to view the parameters that are attached to the asset structure.
Select the “View Attached Spare Parts” link from the bottom of the page, to view the spare parts that are attached to the asset structure.
Select the “View Attached TSGs” link from the bottom of the page, to view the trouble shooting guides that are attached to the asset structure.
Select the “View Attached Task/SP” link from the bottom of the page, to view the task or procedure categories that are specified for the asset structure.
Building asset structure hierarchy – An overview
The asset structure, for which the hierarchy is built, is set as the top most asset structure, in the hierarchy. You can build the hierarchy, by specifying the child asset structures in the multiline. A single asset structure can appear more than once in the hierarchy, provided the asset structure is not a direct ancestor of itself. For example, an asset structure can be a top-most asset structure in one hierarchy as well as a child asset structure in another hierarchy. Or, an asset structure can appear in the third and the sixth levels in the same hierarchy, provided it is not a direct descendant of itself. In such cases, the system provides you with the option of including the already defined child asset structures into the newly created hierarchy.
You can also attach a spare structure to a child structure. You can also enter any other information about including the asset structure in the hierarchy.
“Create Asset Structure Code” activity.
Build asset structure hierarchy
Include or Exclude child asset structures, while building the asset structure hierarchy
Build asset structure hierarchy
You can build a hierarchy of asset structures in this page.
Select the asset structure for which child asset structures must be defined in the “Parent Structure” drop-down list box.
Enter the child asset structure in the “Child Structure” field in the “Children” multiline.
Click the “Next” or “Previous” pushbuttons to attach child asset structures to various parent asset structures in different levels in the hierarchy.
Click the “Submit” pushbutton to define the hierarchy.
Include or Exclude child asset structures, while building the asset structure hierarchy
You can set the option of including child asset structures of the asset structure being copied to the asset structure being created.
Set the “Include Child ?” to “Yes”, to indicate that child asset structures can be included in the hierarchy.
Set the “Include Child ?” to “No”, to indicate that child asset structures must not be included in the hierarchy.