Catalogues and Specifications User Guide
Supports : Hanger Manufacturer’s Design Interface : Hanger Interface Configuration
Hanger Interface Configuration
The Supports application must be configured to work with the appropriate manufacturer’s interface. This is achieved by use of a configuration file called HangerInterfaceConfiguration.xml, which is installed in the standard install path of the product. The configuration file contains different configurations for:
•
Legacy hanger interfaces. For example, CPL and LIS.
•
Generic hanger interfaces.
The example displays a typically structured Witch Hanger interface configuration file.
<Interface id ="CPL">
  <Description>witch hanger 4</Description>
  <ExePath>C:\Program Files (x86)\WH4\WH4WIN.exe</ExePath>
  <LegacyFormat>true</LegacyFormat>
  <LoadDataAttributes>
    <!-- This category stores load data information-->
    <!-- LoadAttributeName is the uda or attribute name to store data against-->
    <!-- LoadAttributeDescription is the description of the data being stored-->
    <LoadAttribute>
      <LoadAttributeName id=":mdsLoad" />
      <LoadAttributeDescription id="Normal Load" />
      <LoadAttributeElementType id="ANCI" />
    </LoadAttribute>
    <LoadAttribute>
      <LoadAttributeName id=":mdsELoad" />
      <LoadAttributeDescription id="Emergency Load" />
      <LoadAttributeElementType id="ANCI" />
    </LoadAttribute>
    <LoadAttribute>
      <LoadAttributeName id=":mdsFLoad" />
      <LoadAttributeDescription id="Failure Load" />
      <LoadAttributeElementType id="ANCI" />
    </LoadAttribute>
    <LoadAttribute>
      <LoadAttributeName id=":mdsHLoad" />
      <LoadAttributeDescription id="Hydro Load" />
      <LoadAttributeElementType id="ANCI" />
    </LoadAttribute>
  </LoadDataAttributes>
</Interface>
The ID of each individual Hanger interface. For example:
Legacy hanger interface
<Interface id ="CPL">
Generic hanger interface
<Interface id ="GEN1">
The description of the manufacturers hanger interface. For example:
Legacy hanger interface
<Description>witch hanger 4</Description>
Generic hanger interface
<Description>generic interface 1</Description>
The executable path of the manufacturers hanger interface. For example:
Legacy hanger interface
<ExePath>C:\Program Files (x86)\WH4\WH4WIN.exe</ExePath>
Generic hanger interface
<ExePath>C:\GEN1\GEN1.exe</ExePath>
A field that indicates if the interface is required to use a legacy file format. Legacy Hanger interfaces require this field to be true. The interface must write files to .WIF/.WOF, .LIF/.LOF, and PSI/.PSO formats. For example:.
Legacy hanger interface
<LegacyFormat>true</LegacyFormat>
Generic hanger interface
<LegacyFormat>false</LegacyFormat>
Fields describing custom load input data that is applicable to the hanger interface. For example:
<LoadAttribute>
  <LoadAttributeName id=":mdsLoad" />
  <LoadAttributeDescription id="Normal Load" />
  <LoadAttributeElementType id="ANCI" />
</LoadAttribute>
In the example, a custom load attribute described as Normal Load is defined. The interface can interpret the Normal Load attribute and can read or store the attribute in the attribute :mdsLoad (which is a standard supports UDA). Other interfaces can be configured to use dictionary data from proprietary databases.
In addition the support element can be referenced to a uda. In the example, the uda is associated with the support ancillary.
Data fields are available to enable configuration of specific functionality for certain hanger types. For example:
<HangerConfiguration>
  <HangerType>
    <HangerTypeNumber id="1" />
    <HangerTypeDescription id="Single Hanger To Single Beam" />
    <HangerTypeConnectivity id="UD" />
    <HangerTypeXyOffsets id="FALSE" />
  </HangerType>
</HangerConfiguration>
Each HangerType field contains configuration information for a single defined hanger interface type. The HangerTypeNumber field stores the number of the hanger that the configuration data is applied to.
The HangerTypeConnectivity field controls the available options for the Hanger Connectivity tab on the Support Editor window.
Valid options are:
•
PD - Pipe Dominant
•
PP - Pipe Parallel
•
TD - Tail Dominant
•
UD - Up/Down
A valid configuration entry could be:
<HangerTypeConnectivity id="PD,PP,TD,UD" />
Note:
: If only one option is available in this field, the associated form tab is not displayed.
The HangerTypeXyOffsets field controls the visibility of the Hanger Offsets tab on the Support Editor window
Valid options are, FALSE or TRUE
Note:
The configuration entries listed should only be modified when appropriately advised by the hanger interface vendor. The associated functionality that this configuration exposes may or may not be compatible with the vendors interface software.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo