Support delayed startup of queries for GE HabConnect Connector
In some EMS configuration it is possible that to connect and query sampler before habitat database has initialized. This can cascade throughout PI -- analytics set to watch for minimum values, applications looking for status changes, etc. It is almost impossible to repair since the source system reported it -- the only way I understand to fix it would be to backfill from eTerra Archive on every failover or startup.
The current interface supports a delayed startup option, which combined with PERMANENT supports some ability to avoid this condition. However a more flexible solution would be an option, by query or across the board, to delay the initial query to sampler after connecting (not based on connector startup). This supports failover of sampler with little data loss and less chance of unitialized data cascading through the PI system.