Design Line uses Node Keywords to associate scenarios on the line. Service Buttons can be allocated a Button Code that will be used as the first point of call when attempting to Fill in the Design Line or to Swap out Services. This topic will walk through how to assign Button Codes and the benefits of keeping Button Codes generic across multiple services.
Each button requires a Button Code for it to be used in the Fill or Swap scenarios. The Button Code drop down menu offers presets for selection which are all common names used internally by the software. When a line is drawn, the Node Keyword will always be uses and display one of these common codes in the lines annotation. For Fill or Swap, checks of the active service are performed for a code of the same name. If no Buttons in the service are identified, Button mappings are used to form combinations of buttons, for each of the Node Keywords.
The benefits of keeping Button codes and Buttons mapping the same across multiple services where possible:
- Allows services to be swapped freely without any missing items.
- Allows the same scenarios to be performed for each Node Keyword.
- Swap out relies heavily on a like for like swap, Button Codes being generic allow for cross service compatibility.
Example
The example above shows a Reducing Tee using a unique Button Code RedBranch-90, as this is non standard, the Fill or Swap routine will not complete unless a Button Mapping is used for the Key node name.
The Reducing Tee is used in a run to reduce the run in size. (See Design Line Button Mappings topic). The Key node used for this would be RedILTee. Unless a button is found in the active service that could accommodate the Reducing Tee scenario and is named RedILTee, the software moves to the next phase of checks within Button Mappings.
Within the active service, the Button Mappings tab is used to identify and capture the remaining scenarios if not already caught by the Service Buttons having Key node names.
Shown below, the RedILTee has been used multiple times to cover all instances of the configured service. The fill will flow from top to bottom when completing the checks in order to find the first possible solution. The RedBranch-90 solution is 3rd in the list, therefore the routine will go through the 1st and 2nd checks first before being able to fill with the RedBranch-90 button. In order for the RedBranch-90 to fill, the 1st and 2nd RedILTee would need to fail, perhaps due to no size in the product list on the buttons attached item.
