Building the L/HIRF Hierarchy

Projects that use MSG-3 guidelines that support identification of L/HIRF Significant Items (LHSIs) — i.e., Revision 2015 Vol 1 (LHSI Identification), Revision 2015 Vol 2 (LHSI Identification) or any subsequent guideline revision — are considered LHSI projects. If your project uses one of these guideline versions, there will be a separate L/HIRF hierarchy, which allows you to identify LHSIs for ATA systems and/or subsystems; L/HIRF environmental damage/accidental damage (ED/AD) analyses can be performed for these LHSIs. To access the L/HIRF hierarchy, click the L/HIRF Hierarchy tab on the System panel.

In the L/HIRF Hierarchy tab, there can be no more than three levels in the hierarchy (system, subsystem and LHSI), and the first two levels must be selected from a predefined list of ATA chapters (systems) and sections (subsystems) that are stored in the database.

Each item has properties associated with it, which are viewed and edited on the Properties tab of the Analysis panel when the item is selected.

Available Columns

The following columns are displayed in the L/HIRF hierarchy:

  • ATA # displays the item number. For systems and subsystems, this is the ATA-assigned number. For LHSIs, this is the value given in the item properties.
  • Description displays the name and/or description of the system or item.
  • Status Updates displays if the item contains any status update notes.
  • Attachment displays a paper clip icon if one or more files or URLs have been attached to the corresponding item. It displays if a Description and Operation (D&O) document is one of the attached files.
  • Flag displays a flag for the item, if desired. The available flags are: Complete (indicated by a green flag), In Progress (indicated by a yellow flag) and Incomplete (indicated by a red flag). In all ReliaSoft applications, flags are displayed in the interface only and do not affect analysis results or reports.
  • User Access displays an icon when the item is inaccessible. (See Status Indicators.)
    • If the item is in use by another user, an in use icon will be displayed. Point to the in-use icon to display the name of the user who is accessing the item.
    • If you do not have the item permissions needed to edit the item, a restricted access icon will be displayed.
  • Environmental/Accidental Damage Analysis displays  if an environmental damage/accidental damage (ED/AD) analysis has been created for the LHSI.

Adding Systems and Subsystems

For compliance with the ATA numbering guidelines, the available system and subsystems have been predefined for the database. (See Managing ATA Chapters.)

  • To add a new system, choose L/HIRF > Add > Add System(s).

  • To add a new subsystem, select a system and then choose Systems > Add > Add SubSystem(s).

Both commands open windows that display the list of systems/subsystems that have been predefined for this database. Use the check boxes to select one or more items to add to the hierarchy and click OK.

Note that each system/subsystem can be used only once per project. So if the item already exists in the current system configuration, the text will be grayed out and you will not be able to select it.

The command to add subsystems will be disabled if at least one LHSI has already been defined for the parent item. LHSIs can be added under any type of record (system or subsystem), but they must always be the lowest level in any particular branch of the hierarchy.

Adding L/HIRF Significant Items

LHSIs are not predefined for the database. Instead, you have the flexibility to create these records as needed for your particular analysis.

  • To add a new LHSI, select the parent item (must be a subsystem) and choose Systems > Add > Add LHSI.

There is no limit to the number of LHSIs that you can add for the same subsystem, and you can use any number for the # field as long as it is unique among the LHSIs associated with that item.

Deleting

To delete an item from any MPC hierarchy, select the hierarchy item and press DELETE. The hierarchy item will be deleted, along with all dependents and all associated attachments. There is no undo for deleting an item or the entire hierarchy.

Cutting/Copying

You can cut or copy items in any MPC hierarchy and paste them to the same project or to another project within the same database. (Please note that if you want to share hierarchy items between different databases, you must use the import/export functionality instead.) To select multiple hierarchy items for cut or copy:

  • Click the first hierarchy item and then press CTRL and click additional hierarchy items at the same level of the hierarchy.

or

  • Click the first hierarchy item, then press SHIFT and click another hierarchy item to select all hierarchy items at the same level of the hierarchy between and including the two.

After you select the hierarchy items, you can use the standard keyboard shortcuts for cut/copy (CTRL+X and CTRL+C) or you can choose Home > Clipboard > Cut and Home > Clipboard > Copy. When a hierarchy item is cut or copied, all dependents will also be cut or copied, along with any attachments.

Pasting

To paste items that you have cut or copied from any MPC hierarchy, press CTRL+V or choose Home > Clipboard > Paste. Note the following:

  • For the top two levels in the hierarchy (i.e., systems/subsystems, structures/substructures or major zones/major sub-zones), each item can be used only once per project. If an item with the same number already exists within the project you are pasting to, you will be prompted to decide if you want to replace the existing hierarchy item or cancel.

  • If a hierarchy item is cut or copied but then deleted from the project, the copied data will also be deleted from the Clipboard. In addition, once a hierarchy item has been cut or copied, any edits that are made to the original will also be applied to its copy in the Clipboard. In other words, if there are changes to the original hierarchy items after you cut/copy them but before you paste them somewhere else, this will affect the data that can be pasted. Also note that you will not be able to cut or copy a hierarchy item in a project that is locked by another user.

Importing

It is easy to import any entire hierarchy (or selected items) from any project in the same database or another selected database. (See Importing MPC Hierarchies Between Projects.)

Related Topics and Links