For the purpose of distributing the results of engineers' work, for a future project or for an existing one. Owning systems as assets is impossible without a clear understanding of what is located where and how the lifecycle is supported. Current tasks can hinder the creation of detailed IT infrastructure designs and the development of an IT landscape. This is very useful for making informed decisions regarding IT assets. System models, especially in UML, allow you to communicate with professional IT analysts and architects.

For the paid service, you receive a configuration description comparable in complexity to 500 UML model elements, not counting the downloaded documents for these models.

These 500 elements include:
- A component model, which describes each software module and its interfaces with protocols, with which software modules interact, and by whom they are loaded into the address space.
- A deployment model, which specifies the computers, servers, and other computing devices on which the software modules in the component model are installed. It also specifies the operating environments in which the software modules run (virtualization, containers, etc.). Physical network connectivity via network adapters and other network devices is specified.
- Configuration elements, such as settings files, etc., are also specified in the models—everything that determines the successful installation and operation of the infrastructure, so that the infrastructure design serves as a guide for your engineers.