Splitting, merging and moving cables

Change cable sections and equipment locations after reviewing the preview results.

Last updated: 10 November 2026

Before you start

These actions require the fiber module and editing permission. In Edit mode, select the cable or relevant node. Each action provides a Preview of its effect on connections and quantities. If records change after the preview, check the updated result again.

Splitting, merging and moving endpoints are blocked when they change the physical scope of a cable with fiber measurements. Resolve the measurement warning shown before proceeding. Measurement records belong to the fiber and endpoint against which they were saved.

Split a cable

1. Select Split in the cable card.
2. Select the split point on the line. Snap to a suitable existing node or choose the location of a new splice closure.
3. If a new closure is needed, complete New splice closure. Inside can establish its placement within a structure; proximity alone does not create that relationship.
4. Enter Section 1 name, Section 2 name and section slack if needed. The first section retains the original cable ID; the second is a new cable.
5. Review Fiber strands to leave cut. Fibers you do not select receive a pass-through splice at the split point. Selected fibers remain open there.
6. In Preview, check lengths, connections to be moved, and assignment and circuit warnings.
7. Select Split to save.

Leave free fiber strands disconnected helps select fibers with no endpoint connections; check the selection. If no slack is entered, existing slack is distributed proportionally. Total vertical length is retained. Measured or design lengths created by splitting are marked as derived, not as new field measurements.

Multipart, closed or self-intersecting lines cannot be split. Resolve the displayed geometry and short-section warnings.

Merge two cables

1. Select Merge in the cable card.
2. Select the highlighted adjacent cable. The cables must meet at the same node, with one ending where the other starts.
3. Under Merged cable, enter Name and, if needed, Total slack.
4. In Preview, check the cable that remains, the one to be deleted, attribute differences and pass-through splices to be removed.
5. Select Merge.

The first cable in the chain retains its ID; the second is removed. The shared node is retained even if it becomes empty. Fiber and tube layouts, cable class, assignment exceptions and reservations must be compatible. Equipment connections or other connections at the shared point may block the action. If a circuit anchor is at an endpoint that will be removed there, address that anchor first.

Other attribute differences appear in the preview; the merged record uses the retained cable's values. A field to be totalled, such as measured or design length, being present on only one cable may block the action.

Move a cable endpoint

1. Select Move endpoint in the cable card.
2. Choose the start or end to move, then select the destination node on the map.
3. Review the connections at the old endpoint. They do not move to the destination; select Remove these connections if you accept their removal.
4. In Preview, compare map length, continuity, the length used for quantities and trace length.
5. Select Move.

The action moves the selected end vertex to the destination node. Other vertices remain unchanged; check the new route separately.

Move equipment to another node

1. In the node card, select Move (to another node, including subtree) on the equipment, then choose the destination node.
2. Under Position at destination, choose an appropriate parent or Directly at node.
3. Review the child equipment and internal connections moving with it. Explicitly select Remove external connections if those connections need to be removed.
4. Check splices that will become unpositioned and select Move.

Child equipment moves with its parent. External connections are not extended to the new node. Afterwards, adjust connections and tray positions in the splice diagram if needed. Review completed actions in History; undo is also subject to current connection and data rules.