Today is:   Sep 25, 2018

Brief Banners

Institute Mihailo Pupin
Institute Mihailo Pupin is the leading Serbian R&D institution in the field of Information & Communication Techologies.

Automation & Control Systems Ltd
The Automation & Control Systems Ltd is the core division of the Institute Mihailo Pupin, and the owner of the VIEW4 application.

The long list of the Institute's references and customers is the best proof of its high professional and techological achievments.

ATLAS Systems
The other related IMP project: ATLAS Systems (ATLAS-MAX & pikoATLAS) provides the underlying RTU and PLC infrastructure needed for VIEW4 control implementation

You are here:     VIEW for You Organization

VIEW4 represents a complex software package organized as set of manageable program entities with specific missions, which mutually exchange data through the predefined software interfaces: protocols, standards and system rules.  Such “modular software organization” is fully implemented top-to-down, resulting in the high VIEW4 flexibility and scalability, easier system maintenance and upgrade, and more powerful and cost-effective implementations.  The major software entities are:

  • VIEW4 CORE – the central, application resident portion of the software that provides runtime environment needed for the functioning of the VIEW4 SCADA system.
  • VIEW4 MODULES – large rounded application program entities dedicated to the specific well-defined VIEW4 jobs (groups of tasks).
  • VIEW4 PLUGINS – application program entities dedicated to the specific VIEW4 tasks (or functions).  The major VIEW4 plugin feature is an easy implementation - as the name colorfully suggests, a plugin could be simply plugged/unplugged into/from the running VIEW4 application.
  • VIEW4 TOOLS – a number of configuration utilities, editors, diagnostic and maintenance programs, online and offline utilities, and other support programs.


Many of the listed software entities are designed as master/slave applications.  The master/slave approach allows flexible allocation of the program entities, based on the implemented SCADA configuration.  It means the very same entity could be easily adapted to any runtime environment: the strictly local, or the distributed (remote) one.