When an item, such as a motor, has KKS naming, and you make an electrical association, for example to an MCC or a control station, the software automatically propagates the naming to the associated item. The software also propagates naming when you create a hierarchy such as PDB > Bus > Feeder in the Electrical Index and then rename the source item. The following table shows how the software handles propagation, along with naming examples.
|
Target Item Type |
Inherited Components of Target Item Name |
Possible Source Item Types |
Example of Source Item Name |
|---|---|---|---|
|
Bus |
All populated segments of PDB tag |
PDB |
|
|
Cell |
All populated segments of bus tag + number in group |
Bus |
|
|
Control station |
KKS System and Equipment Unit Codes |
Associated equipment |
|
|
Feeder circuit and internals |
Load item tag + KKS segments |
All loads |
1 0PAC01 AP01B –E01 (heater) |
|
Instrument |
KKS System and Equipment Unit Codes |
Associated equipment |
|
|
Space heater |
KKS motor naming + heater component code, for example: 1 0PAC01 AP01B –E01 |
Motor |
1 0PAC01 AP01B –M01 |
|
Incomer circuit and internals |
Upstream power source KKS tag segments |
Upstream power source |
|
|
Transformer component |
KKS System Code of connected item + KKS numeric segments for secondaries, for example: GT002, GT003 |
Transformer (main item) |
GT |
|
I/O signal |
KKS System and Equipment Unit Codes + signal application / origin code |
Motor, feeder circuit, control station, instrument |
For more details of how propagation works, see Examples of KKS Naming Propagation.
-
The software performs propagation according to hard-coded rules. Name segments that are not included in a propagation rule remain blank.
-
On connecting a cable side to a load or a panel, the KKS naming is propagated to the cable. When both sides of a cable are connected, the naming comes from the first alphabetic item. On disconnection, the cable retains the name it received by propagation until you reconnect it.