Citect SCADA

Customer voice & ideas portal

Object oriented equipment editor with nested objects (equipments)

When having equipment types that are similiar, today you can either make a copy with the differences (hard to maintain) or for some cases making optional signals through the xml can be done.


What would be nice is to add an equipment type in another type, so that you can define a processvalue (PV) equipment type once, with trend / alarm and necessary tag structure once. Then in other equipment types instead of re-creating 10/15/20 times or however many signals you need, you paste the PV equipment type where most of the information is handled in that equipment type.

EquipmentType PV

processvalue with trend and alarm - no type

supporttag for alarmblocking - no type


EquipmentType Motor

PV1 - type PV

PV2 - type PV

CMD - no type


EquipmentType Motor_special

motor - type Motor

extrasignal1 - type PV

extrasignal2 - no type


  • Guest
  • Sep 2 2026
  • Submitted
Idea business value
  • Faster creation of new equipments with the use of predefined PV/SP/CMD/STS types ready for use. Less errors / headache maintaining similiar equipment types.

  • Less time creating tools outside of plant scada to handle tag generation.

  • Higher overall quality for end user.

Idea priority 4 – Important to my company
  • Attach files