Designing SCADA systems can be a challenge. When developing or updating a SCADA system, it is important to consider which devices it will need to communicate with, how and where the application HMI is required, as well as the disruptiveness of component downtime or missing historical data. With these items, one can start the process of planning their application architecture. Of course, it is good to consider that the architecture should be flexible enough to support the progressive updating. In this video Dave Spencer reviews the architecture for common VTScada systems. As we progress, we'll also lay out the VTScada pricelist components required to build a system with this architecture.