Skip to Content

7.6.10. Automatic annotations in views and isos

Updated on 07/09/2026

On this page

    Automatic annotations in views and isos

    Learn how you can manage specific annotations for different views in Plant 3D. Since the default behavior of the software has certain limits, an understanding of the configuration options is essential for consistent project standards.

    Background

    Plant 3D does offer an automatic annotation function, but it is not controllable per view. This means that the annotations are assigned project-wide according to uniform rules and a separate definition per view type (e.g. Front, Side or Iso) is not natively provided.

    Prerequisites

    • Basic knowledge of creating ortho views in Plant 3D
    • Access to the project configuration to define standard annotations

    Step-by-step guide

    Since a fully automatic, view-based control is not supported on the software side, the following procedure is recommended to implement your requirements:

    1. Generate base annotations: Use the automatic annotation function of Plant 3D to enter the basic information consistently in all views.
      Result: All components receive the base tags defined in the project standard.
    2. Manual addition for specific views: Navigate to the affected view (e.g. a side view). Add or change the desired additional information, such as the z coordinate (height), manually via the annotation tools.
    3. Specific labeling in isos: In the iso display you can analogously add the pipe number or other specific attributes manually that go beyond the global standard.

    Important notes

    • Default behavior: The described behavior corresponds to the standard of Plant 3D and cannot be switched to a fully automatic, view-dependent logic with built-in tools.
    • Project standards: Define internal conventions in your project team to determine which information must be manually added on which view types.
    • Efficiency: Always use the automatic annotation as the first step to keep the manual effort as low as possible.

    Troubleshooting

    • Missing information: If automated fields remain empty, check in the data manager view whether the corresponding properties (e.g. pipe number) are correctly stored on the 3D object.
    • Annotations disappear: Make sure that after manual changes the view is not completely regenerated without locking or saving the annotations.

    Still a question open?

    Write to us, we answer within 24 hours on business days.

    Request a consultation