As described here
Distributed Local Historians – The County was also concerned about the potential loss of data should the connection to remote sites be lost. In response, MPE configured the application to allow for use of VTScada as local HMIs at all remote stations. Once VTScada is deployed as a local HMI, if the station is cut off from the central application, the local HMI continues to provide local monitoring and control while collecting alarm and historical data. When communications to the local site are restored, all local alarm and historical data is backfilled into the central SCADA system. This was completed for one of the major pump houses during this project. To implement this solution, MPE supplied and installed a local panel mount PC, replacing an existing HMI at the local station. “It’s running the same VTScada application as the centralized servers but using tag and alarm area filtering to reduce the license cost and present only relevant information to local operators,” says Spencer. “Using VTScada as an HMI replacement, and structuring the tag database appropriately, we have effectively implemented historical store-and-forward allowing the County to eliminate data loss when communication links to the station are disrupted. An added benefit is the synchronization with the central system; all graphics, user accounts, alarm history, and alarm configurations are synchronized in real-time. The SCADA application is pre-structured to allow for this configuration at all remote sites and the County would like to implement VTScada as a local HMI for all stations in the future.”
I am looking to do basically the same thing as described here but haven't figured out how to change the tag count at a secondary station. Any help in how this kind of configuration is accomplished?