Usually when using signals associated with positions via code instructions, signal states remain in their active state when moving away from the positions.
Therefore, the signals have to be managed to prevent false indications for position reporting.
When using workspaces as Alexandru suggested, these are effectively controlled on/off via the TCP location reference to the workspace cube defined area.
When you get around to use this function, after visiting the location and turning on the signal(s), can you confirm if the signal(s) automatically turn off when you move away from the location or do they retain their state?
I'd be interested to know if this is the case, if it is then signal management is not required and this would be a very good feature to implement in future installs.