This document offers answers to the most common audit questions.

A brief introduction to D2000 and its architecture

See 

• https://d2000.ipesoft.com/introduction
• https://d2000.ipesoft.com/architecture
• https://d2000.ipesoft.com/blog/scada-architecture-dodm

Structure of D2000 systems in our factory

The answer to this question is very factory-specific, here we offer two possible configurations:

Scenario 1

Currently, there are 3 independent (though interconnected) systems in <Our_company>, built using D2000 technology:

• <System1>
• <System2>
• <System3>

All three D2000 instances run physically on three independent execution servers, which run the hypervisor for the virtual servers needed to run the D2000 system. Each D2000 instance has its own application server, which is redundant and runs physically on a different server, and individual users connect to these application servers. New installations and updates for D2000 are distributed to users via FTP updates from a special server. D2000 is a fully redundant system in terms of application, archive databases, and network optical connections.

Scenario 2:

Currently, there are 2 independent (though interconnected) systems in <Our_company>, built using D2000 technology:

• SCADA
• MES

The SCADA application runs on 3 physical servers (2 of them are in the primary location, the last one is in a disaster recovery location). The two servers are connected to 2 redundant networks, and the DR server is connected to a single network. 

The MES application runs on 2 virtual servers located in the primary location. These servers (Linux) also host a PostgreSQL application database, that also contains the EDA database (energy database working with vectors).

Operators of the SCADA application are also connected to the redundant network, whereas users of MES are connected via redundant Security Access Proxy Servers running on virtual servers located in a DMZ network.