To connect two duct runs using Move :
-
For inline connections, the two duct run ends must be collinear to each other.
-
For branch connections, the header and branch runs must be orthogonal to each other.
-
There should be sufficient space at the connection to accommodate the connecting part. If the space is not sufficient the software does not make a connection and displays a message suggesting to connect the duct runs manually.
-
The software consumes the first available straight feature of the moved duct run to accommodate the connection thickness, such as a mating part.
-
In a partial move, if the connection results in an overlap the software connects the two ends with a To Do Record while maintaining the connectivity.
-
If there is no space to accommodate the mating part, the software does not connect the two ends and displays a message suggesting that you connect them manually.
Inline Connection
No. |
Route Object |
Approval Status |
Permission Group Access |
||
---|---|---|---|---|---|
1 |
Duct run A |
Working |
Full control/ Write |
||
2 |
Duct run B |
Working |
Full control/ Write |
||
3 |
Reducer connecting duct runs A and B |
||||
Result: The software connects the duct runs A and B using a system-generated transition. Reduction in duct run B length = length of the transition. |
|||||
Branch Connection
No. |
Route Object |
Approval Status |
Permission Group Access |
||
---|---|---|---|---|---|
1 |
Header run |
Working |
Full control/ Write |
||
2 |
Branch run |
Working |
Full control/ Write |
||
3 |
Horizontal tee connection associated with the header |
||||
Result: The software connects the header and branch runs at the tee end feature. |
|||||