Project validation enables a cluster or the entire project to be checked specifically for technical, topological and data-related inconsistencies. This function helps to identify and rectify missing mandatory details, incorrect links, implausible names and topological problems at an early stage.
This function is particularly useful before quality checks, data exports, transfers to downstream processes, and whenever the data consistency of a planning status needs to be verified.
Project validation is accessed via the NET tab in the ‘Edit features’ group.
The following dialogue box appears:
(1) You have the option to select a specific cluster. If no cluster is selected, the validation is carried out for the entire project.
The validations are divided into three thematic groups:
(I) Data checks
(II) NET Engineering
(III) TKI NET Build
The validation can be carried out for all groups, individual groups or sub-groups, or for individual checks.
Within the data checks (I), there is a section entitled ‘Data checks for NET Engineering’.
The section ‘Data Checks for NET Engineering’ (II) is in turn divided into the following sections:
| Fiber Optic Network | Status Consistency | Survey plan | Telephony |
| Building postcode | CX Cable ends | CX Kabel without assigned ducts and cables | |
In the ‘NET Engineering’ section (II), cables can be checked for their cable endpoints.
In the ‘TKI NET Build’ section (III), specific tests can be carried out on segments, ducts and buildings before the data is exported.
In the lower section, with a single click
(2) all checks can be enabled,
(3) the validation can be started, or
(4) the dialogue box can be closed.
The process can be cancelled at any time during validation:
After the validation has identified the issues, the results are displayed grouped by validation category. Checks without errors are highlighted in green, while checks in which errors were found are highlighted in red.
The checks highlighted in red can be expanded to review the individual messages in detail.
The messages vary depending on the check:
Each error message refers to an affected object.
A context menu can be opened for both the groups and the individual messages:
| Group | Individual message |
The context menu of a message can be used to open the object form. Depending on the configuration, the object can also be highlighted on the map or zoomed to.
In addition, tooltips help users interpret individual checks and messages.
A warning symbol does not necessarily indicate a technical error in the data. It often points to missing attributes, incomplete links, or deviations from naming conventions.
Troubleshooting
Recommended troubleshooting procedure
First, run the validation for the entire cluster.
Start with messages indicating missing links, topology errors, or invalid geometries.
Next, correct mandatory attributes and naming errors.
Run the affected validations again to verify the corrections.
For recurring messages, document whether they are caused by data errors, modelling errors, or project-specific exceptions.
It is advisable to rerun the validation after each round of corrections. This makes it easy to determine whether subsequent errors have been resolved or whether additional objects are affected.