This functionality is only available for certain module packages.

You are here: Concepts > Functional configuration > Structuring project documents

Structuring project documents

Whereas the construction hierarchy of a machine or plant is structured based on functional criteria, the project documents for the various disciplines are generally structured according to different criteria. This is illustrated by the following example.

In mechatronic construction, BOMs are created that are structured based, for example, on assembly-related structuring criteria. The goal of this structuring is to organize all of the components required for a subassembly into a single branch in the hierarchy. This allows ordering and assembly to take place at different locations, for example.

By contrast, the schematics diagram is organized based on device-oriented structuring criteria. A section of the plan contains, for example, all of the controller’s input and output cards along with each of the connected sensors and actuators.

The software, in turn, is structured with different perspectives in mind.

It may be noticed, for example, that a gripper is represented at very different locations in various project documents.

These cross references require interdisciplinary coordination, which, due to the current lack of adequate system integration (isolated solutions), quickly leads to inconsistencies in databases, even when changes are made during later project phases.