← Library EQUILIBRIUM equilibrium-system.com

Russian Government Order — Construction

Order of the Government of the Russian Federation No398-r from 2 March 2026

The strategic direction of digital transformation in two key industries:

These are not just “plans” — they are a framework through which money, projects and regulations will now be distributed.

The essence of strategy (simple language)

The State says:

"We are converting construction and housing into a digital system"

Key directions

Unified digital environment of construction

This directly falls on your idea of a Digital Single Operator

Compulsory BIM / digital models

No longer a question of "need or not" - this will be the standard

Registers and data

You have already moved in this: Register of construction = core system

Digitalization of housing and communal services



This is the second half of the system - operation after construction

Platform-based approach

This is a direct confirmation of your architecture:

marketplace + ACS + registry

Reduction of time and morning

The state wants:

Building faster and cheaper with numbers

What this means in practice

It's not a theory, it's a signal:

1. There will be money

State funding will go to:

There will be mandatory standards

3. The market will be rebuilt.

It's an important moment (honestly). The state is now making a base, but:

And here comes the window of opportunity.

Where is your entry point

To put it bluntly, you’re right where you need to be right now.

Your concept:

This is 100% coincides with the vector of the state, but:

you have a higher level - system + semantic

How to use it strategically

Positioning Not a "startup", but:

Integrator of the strategic direction of the Government of the Russian Federation No398-r

Product assembly (very important)

You need to collect MVP from 3 blocks:

Access to the State

You can enter through:

Next step (specific)

You can't spray now.

Need:

. assemble one demonstration circuit

For example:

"Digital construction of the object from the application to the input"

Hard Conclusion

In short:

And here's the important thing:

Or you become an architect of the system.

Or you'll be built into someone else's.

We go into the application layer: the architecture of the platform for state tasks, not as an abstract marketplace, but as an outline, which directly falls on the strategic direction by order No398-p.

According to the document, the focus is to bring the construction and housing sectors to "digital maturity", reduce the investment and construction cycle and costs due to TIM and AI, transfer administrative procedures to electronic form, develop electronic processes in housing and communal services, and build cross-industry solutions on the GosTech platform. Separately mentioned are the industry platforms "Construction Management" and "Utilities", as well as the development of housing and communal services management based on GIS and "Public Services House". By 2030, the share of positive conclusions of the state expert examination on documentation in the form of 3D-information model is planned at the level of 95%. 

How the platform should be set up

I would collect it not as one "monolithic portal", but as a single digital circuit of 5 levels.

Level 1. Registry-core

This is the main layer. Without it, everything else turns into a set of disparate services.

What is included:

This corresponds to the logic of the document: the state does not need separate files and offices, but end-to-end digital data for construction and housing and utilities. 

Level 2. Process layer

This is the ASU that guides the object in stages.

Key processes:

Here, the platform should provide not just storage, but process routing, timing control, statuses, roles, deadlines, locks, and automatic checks. It is this layer that is responsible for the task of reducing the duration of the investment and construction cycle. 

Level 3. Digital Object Model Layer

This is a separate circuit under TIM/BIM/digital twin.

What should be:

Since the document directly relies on TIM and indicates the target for state expertise of 3D models, this layer cannot be made a “complement”. It should be central, not decorative. 

Level 4. Service layer of interaction

This is what the user sees as a platform.

Services:

This layer is needed for the complete translation of administrative procedures into electronic form, which is directly stated in the materials by order. 

Level 5. Analytics and AI

Not a "fashion add-on", but a management tool.

What gives:

The document directly links the loss reduction with the implementation of AI, so that without this, the platform will already lag behind the target framework. 

Platform Target Model

The core of the platform is better described as follows:

A single platform for managing the life cycle of an object from initiative and design to construction, commissioning, housing and utilities and overhaul.

That is, not just a "construction", but the construction of + municipal infrastructure + operation. This coincides with the two industry tracks that are fixed in the strategy: "Construction Management" and "Utilities". 

What modules should be in the MVP-state version

In order not to spray, MVP must be made from 8 modules, not 40.

Module 1. Object passport

One digital passport per object:

Module 2. The route of the investment and construction cycle

Step-by-step funnel:

Module 3. TIM/Model

Module 4. Examination and approval

Module 5. Construction control and execution

Module 6. Utilities

This is important because the strategy separately displays the contour of the municipal infrastructure as an independent digital track. 

Module 7. Operation and Housing

The logic of the document is precisely not to break the digital chain at the input of the object. 

Module 8. Analytical Center

Role model

Without a clear role model, the state platform quickly collapses.

Basic roles

Critically, each role should have its own screen, its own set of actions, its own registry and its own KPI. Not a common office for everyone.

Integration scheme

Under the state tasks, the platform should not be a closed system, but an integration hub.

Minimum integration contour:

Since the strategy separately stated cross-industry solutions based on "GosTech", the architecture should be designed immediately as API-first platform. 

Data Logic: What is a “Single Entity”

For the platform to work, you need to hard fix the main data entities:

The whole system should not be built around folders with PDF, but around these entities. Then you get end-to-end traceability from design to operation.

Where you can have a strong position

If you collect architecture under the entrance to the state agenda, then your strong formula sounds like this:

Not “another service for construction”, but “operating platform for the execution of order No. 398-r at the regional/industry/operator level”.

It's stronger and more accurate. Because the strategy already sets the demand for:

Practical positioning option

I would put it this way:

Unified digital platform of construction management and housing and utilities

for authorities, developers, technical customers, contractors and operating organizations,

providing end-to-end digital life cycle of the facility, electronic administrative procedures, work with TIM models, management of municipal infrastructure and analytical control of project execution.

It is not a concept language, but a product.

What to do next

The most correct next move is not to write another 100 pages, but to collect the structural scheme of the platform in 3 layers:

Then you can do: