About Line IDs

A Line ID (Logical Line Identification) is a logical object which is used for identifying and organizing segments of a HVAC design and the components and equipment you place in them. All the components and equipment in a line ID have the same defined characteristics (attributes).

The Line ID displays in the tree as an organizational element. The routes you create and the components you place under it appear in the tree, and are displayed as 3D images.

An example of a Line ID and its attributes (for an avionics project) is shown below:

• Discipline: HVAC
• System: Ventilation
• Subsystem: Cooling
• Function: Main exhaust
• Attribute "Standard": MM
• Attribute "Equivalent Diameter": 100
• Attribute "Duct Specification": Ti

A Line ID facilitates the creation of ducts and selection of parts. When you create a Line ID, you set the attributes you want to use for a logical section of your HVAC system. The common attributes are Standard, Equivalent Diameter and Duct Specification (other attributes are Operating Pressure/Temperature and Duct Insulation Specification).

Whenever a duct is created or a part is placed in this logical section of the HVAC system, its Standard, Equivalent Diameter and Duct Specification attributes are taken automatically from the Line ID. This "automation" helps maintain designer productivity and constrains the design process by imposing predefined design rules.

Line IDs have to be created in a logical reference of an RFLP tree.

An example of a logical tree for some of the fluid systems in an avionics project is shown below:

• The first level is called PROJECT A Logical Lines (or simply Logical Lines if those markers are common between all projects).
  
  
• The second level is for the main systems (Hydraulics, Fuel, Environmental, etc.).
  
  
• The third level is for the subsystems (landing gear, wheel brake, flight controls, doors, etc.).
  
  

You create Line IDs at the appropriate positions in this logical tree.

There is a number of ways to create a Line ID; your choice depends upon where you are working in the RFLP tree (logical or physical):