Typical System Architecture

Typical System Architecture
A typical system configuration is equipped with a Microsoft IIS server. A virtual private network (VPN) server connects the development team to the system remotely. The VPN also allows users from the corporate office to oversee plant operations from any location.

  A Virtual Private Network (VPN) server makes your application accessible to you but not the outside internet
  Data can be sent to a large display so everyone can view it from a central location.
  The development team provides prompt service by connecting remotely through VPN.
  Software on portable devices (ipads, laptops, etc.) make it possible to control equipment from anywhere in the plant.
Corporate personnel can log in and see what’s going on at various plant locations.
  Local managers can see everything on their desktops from their office.
  The mail server can be configured so that it sends specific alarms to specific users.
  Every time a user logs on, visits a page, or makes any changes to the system, it gets recorded in the User Log.
  Operators can easily monitor plant operations from a central control room.
  Microsoft IIS is configured locally on a virtual machine. The web portal to the web application (TagsCollector) is set to port 80. A dashboard display is optionally configured to use port 80xx.
  TagsCollector shares a limited number of files between itself and IIS, including XML, CSV, and memory mapped files.
  A configuration file tells TagsCollector the addresses of the PLCs and what the tag names should be.
  TagsCollector connects with the PLCs, collects data, and automatically formats it to records trend and performs analytics.

Teronus Inc © 2006-2019