Types of infrastructure for deploying automated systems

Working with IT managers, I discovered that there is often no understanding of the types of infrastructure that are necessary for the deployment of automated systems (AS). As a result, errors occur in planning the development and deployment of AS – some types of infrastructure are overlooked: they are not taken into account in projects, technical specifications are not requested, use is not agreed upon, there are no contracts for the use of the necessary infrastructure, etc. Errors also occur in the distribution of responsibility during the operation of the deployed AS, when part of the infrastructure ends up “no man's land” because they forgot to agree on its maintenance.

In order to provide explanations to the specialists I had to work with, I created a simple hierarchical diagram that I would like to share with the public. It is good for educational purposes or for a quick project assessment. The diagram is shown in Figure 1. This diagram clearly shows what types of infrastructures exist and breaks down the AS into 5 types, depending on the types of infrastructure used.

It should be noted that the hierarchy at each enterprise will depend on the distribution of responsibilities between the operating and servicing departments. For example, a cable tray can be either a structure or a network or engineering infrastructure, depending on who services it (I am not commenting on this, this is my experience). Here I classify it as a structure.

Types of infrastructure:

Buildings and industrial equipment – buildings are located at the very bottom of the hierarchy, this is the “box” in which everything else is placed. Industrial equipment is placed in buildings.

Buildings – are usually placed on buildings. First of all, these are various metal structures: masts, mounts for video cameras and sensors, cable trays, etc.

Engineering infrastructure – everything that ensures the functioning of technical equipment: power supply, cooling, communication racks, etc.

Network infrastructure – this includes technical means that ensure information interaction (switches), data networks, communication lines.

Information and computing infrastructure (ICI) – technical means and software intended for general and special software (GSS and SS). This is computer hardware, operating systems, and the like. This also includes “clouds”.

SPO (special software) – software that runs on the IVI. This may be software that is necessary for the functioning of the AS or that is modernized by the implementation of the AS.

At the very top of the hierarchy is the AC itself.

Now about the division into classes (a class with a lower number includes all classes with a higher number that are higher in the hierarchy):

Class 1 – all types of infrastructure are required for AS (though I have not come across AS that require building construction). Example: AS for analyzing information from video cameras within the city. Cameras can be installed anywhere, including on industrial equipment (for example, on a traffic light).

Class 2 – AS, which requires equipment or modernization of the communication room (server room) with the installation of racks, additional air conditioners, etc.

Class 3 – AS, which requires integration with adjacent systems. This requires network configuration and/or installation of additional switches. This class is probably the most common (let's not forget that all classes with large numbers are included in this one).

Class 4 – An AS that is located on a newly installed server (with an OS, containerization, etc.). This includes AS that are located in the “cloud”.

Class 5 – an AS, for the functioning of which special software must be installed on the server or which upgrades the existing software. Example: a module with AS functions for the existing software (for example, a module for 1C).

The first thing that is required when planning the deployment of the AS is to correctly determine the types of infrastructure that can be used. In the future, it will be necessary to determine the conditions for using this infrastructure – request TU, conclude contracts for use and maintenance. Also, infrastructure modernization is often required, which must be planned in advance. It often turns out that modernization issues arise on the go, because they were simply forgotten. And this is a shift to the right, money and nerves.

Example: there is a workshop with IoT sensors installed. Information from the IoT sensors is stored in a database. The database is accessible from the LAN with a login and password. There is no free server in the server room, but there is space in the rack. There are reserves for electricity and cooling. It is necessary to make an AIS (automated information system) that will process data from the sensors and display the results on the screen. This is class 4, since all that is required to create an AS is to create software and install a server for it.

Of course, the diagram above is very simplified. Some infrastructure types may be excluded because they are ready. Some may be broken down into subtypes because they are divided between different service organizations. But this diagram can serve as a good starting point for analysis and planning, especially for beginners.