>  Running it all through one or more central VVX server(s) would be cumbersome   Also remember that ViewX runs on the VVx server so connecting from the central server over the high latency links might not be as performance happy as you might want. ... View more

This comes down to how you structure your templates. The simple way is a flat structure and so in your case it might be best to create a second template. You can look into using abstract points in your template and converting in the instance, but this might be time consuming with too many points and too many instances.   The better way might be to have a more structured template, i.e. define templates for your blobs and create instances of those within a template. You'll still need multiple templates but by bringing in a common template for say RTUs and mimics, and then also for Pump type 1, type 2, etc it provides a very modular setup. The first time you see it it looks confusing, but as you have a common template across multiple "parent templates" maintenance becomes much easier.   For example, create templates for:   * RTU * Displays * Site Reports * Pump Type A * Pump Type B * Pump Type C * Valve Type A * Valve Type B * Valve Type C   Then create a parent template which is just a grouping of instances, and would consist of the first three always, then pick and choose from the others as necessary to build that example site. Then create a second parent template and again pick the first three, and another mix.   If you have no consistency across anything this is probably really inefficient, but if you have standards on site construction it can be really powerful especially when you're dealing with many hundreds of sites. ... View more

The quick answer is "it is usually logic or file flushing to disk", so check you don't have some crazy logic running too much (Queries -> Logic Execution Status) and that you have anti-virus definitions configured correctly as per https://tprojects.schneider-electric.com/telemetry/display/CS/Anti-virus+Scan+Exclusions   So, with wild speculation aside, if you're running a version released in the past couple of years you get some funky lock analysis tools. You can enable LCK/Lock logging in the DB log files since forever but this new function does a pivot table on that so is much better for identifying the effect and then you can drill down through the logs for the cause.   What I recommend is:   1. Go to Server Status 2. Go to General -> Logging 3. Enable LCK/Lock logging (note this will drastically increase the amount of logging on your system which may impact performance and will cause DB log files to roll over much quicker, so make sure you have sufficient DB logs configured) 4. Still in Server Status go to Database -> Lock Diagnostic Read and also Write (in recent versions its two windows, previous version it was one). Right click on each one and choose "Enable Diagnostics" 5. Let it run for a bit (probably not too long in your case given you said always active) 6. Check out the screen for anything which is...    a. Longest [Read|Write] Lock is > 1000mS  b. [Read|Write] Locks Per Second is > 1 (note that things like InterestThread are probably more than 1, depends on what clients you have an what they're doing)   7. There might be something obvious, but I'd recommend you open a support case with the logs and then they can take a closer look (you will need to provide the DB logs with LCK logging enabled and DBSnaphot files which capture some of these Lock Diagnostics in) 8. When you aren't looking at it, disable LCK logging. The Diagnostic tabs you can leave as necessary.   There is a setting to reset the Diagnostics tab each snapshot, its probably not that useful for this short time frame analysis but support may ask for it.   Just for some info. The difference between read and write locks is you can only have one write lock active on a system, but you can have multiple read locks active concurrently. You can't have read and write locks active at the same time. This makes write locks very dangerous if they get out of control and are usually the cause of the system locking up for periods of time.   There are some "read" actions that are done under read locks for very specific reasons. Flushing data to disk is a write lock and so when anti-virus starts to interfere with the file writes that can have a serious effect.   If you have a high lock alarm but you're not having the system lock up you're probably looking at lots of read locks happening. ... View more

Hmm, not aware of a nice way. Sounds like you need something in the animations using an IIF, something like for a visibility   IIF(REGISTRY('DEBUG',0) > 1, 1, ".Point.CurrentState")   That way its "client side" rather than reacting off a database object. You should probably provide some script to set and unset the debug flag, recent versions have changed the way the REGISTRY stores data so its now stored against the user profile rather than actually the Registry. ... View more

You probably should raise it as a bug through your support channels to make sure its recorded correctly and tracked.   As an aside someone here might be able to think up a workaround, but I don't have any ideas of any, currently. ... View more

You could specify a layer that's not Enabled but the default layer. When you open in design mode the hidden layer will be visible, but open in run mode it'll be hidden. In design mode you can select the other layers to hide the disabled layer again.   I've seen this used on a couple of systems to provide design note and guidance. ... View more