Maintaining Industry Model / 1-Click Maintenance

1-Click Maintenance is available for maintaining existing factual and geometrical data. This should be done at regular intervals. 

In Autodesk Infrastructure Administrator, start the check under the entry “1-Click Maintenance”. Set a check mark for all checks and start maintenance by “Scan for Issues”.

Admin_1KlickWartung_engl.png

Any problems found are displayed and can be fixed by clicking on the “Fix Issues” button.

If problems are displayed that cannot be fixed, clicking on the appropriate line opens further information on the error.

 

Selected 1-Click Maintenance

Invalid Database Objects

If there are database objects, that are incompatible with the underlaying database management system. If invalid objects are found, and can't be run (anymore). It will try to recreate the affected objects.

Industry Model Dictionary

There is a dictionary inside the database. This lists all feature classes. If there is a feature class, in the dictionary, that is not existing, it will be tried to create this feature class or if there is a feature class, that is not in the dictionary, it is added to the dictionary.

Industry Model Attributes

This 1-Click-Maintenance compares all attributes in the existing feature classes with the table 'TB_ATTIBUTE'. If it is not in there, this will add it during problem solving.

Industry Model Relations

Like the 1-Click-Maintenance before, this one checks internal relations inside of the database. This will remove relations from the mentioned table, if they are not present in the database anymore.

Utility Models

There are a lot of objects in the database, that are linked to a geometry. If a problem is showed here, there are objects, that should be linked to a geometry, but aren't or geometry objects that are not linked to a feature object, which should be the case.

Check triggers

A trigger activates a refreshing in connected feature classes and in the display. This 1-Click-Maintenance checks if the expected triggers are present. If they are not, it tries to create them - if solve problems is used.

Spatial configuration

This maintenance ensures that coordinates are entered with the correct coordinate reference. After creating a new industry model, or importing an existing one it might happen that geometry data is not properly safed without this maintenance done.

TB_UFID

The clean up of TB_UFID removes all entries, that are not necessary anymore. As well it adds missing entries to the table.

Industry Model Sequences

This checks if all the sequences in the industry model. It mainly checks if the next value is right or not.

Form Check

Form Check validates the form data. It checks if the relating feature class, view and attribute still exists. It will tidy up or delete the form if necessary. 

NET Engineering: Buildings

The buildings are checked the following way in this 1-Click Maintenance: It sums all the entries in the building form for existing units (e.g. living and business units) and compares the resulting amount with the entries in the table "TC_TG_BUILDING_UNIT" that are linked to the building. If there is a discrepancie it shows a warning.

less entries in building unit table than sum of units

If there sum of the units is larger than the related entries in "TC_TG_BUILDING_UNIT" to a certain building, a click on "Fix Issues" will create the missing entries in "TC_TG_BUILDING_UNIT". So that the sum and the number of units is equal.

More entries in building unit table than sum of units

When the number of entries in the table "TC_TG_BUILDING_UNIT" exceeds the sum of units of a building, then the issue will not be fixed. When you then select the entry with the unsolved issues, in the lower part of the window a summary of the affected buildings will be shown. There is nothing deleted, since the 1-Click Maintenance will neither decide which is the correct number nor select an entry to be delited - because it is not sure which one shall be kept. This summary can be exported with a right click in this part of the window.

NET Engineering: Missing Attributes

If you click on "Scan for Issues" this 1-click-maintenance checks every object class. The check performed is, if the following attributes exists. The attributes are "Date created" (DATE_CREATED), "User created"  (USER_CREATED), "Date Modified" (DATE_MODIFIED) and "User Modified" (USER_MODIFIED).

If these attributes are not present, a warning is shown. A Click on "Fix Issues" will create this attributes in the object classes, where they are missing.

NET Engineering: Check duct insertions

This 1-Click Maintenance finds discrepancies between the duct reference of a duct insertion and the corresponding topology entry, which can occur due to data errors in the project. There are basically 4 possible cases:

Admin_1KlickWartung_NET Engineering_Rohrabschlüsse prüfen_engl.PNG

  1. The duct insertion is topologically linked to the duct (has a matching topology entry in the TC_CONN table), but the "duct" attribute (FID_DUCT) in the duct insertion is empty. This problem is solved with 1-Click Maintenance by storing the matching duct in the duct insertion.
  2. The duct is stored in the duct insertion, but the corresponding topology entry is missing. This problem is solved with 1-Click Maintenance by creating the appropriate topology entry in the TC_CONN table.
  3. The data for the duct in the duct insertion and the corresponding topology entry in the TC_CONN table contradict each other. This problem cannot be solved by 1-Click Maintenance, as it is unclear which data is correct. In this case, either the duct in the duct insertion (TC_SP_DUCT_INSERTION.FID_DUCT) or the corresponding topology entry in the TC_CONN table must be corrected manually in the SQLSheet in the Autodesk Infrastructure Administrator.
  4. A duct is stored in the duct insertion that does not (or no longer) exist. This problem is solved with 1-Click Maintenance by deleting the duct in the duct insertion (TC_SP_DUCT_INSERTION.FID_DUCT) and, if necessary, the associated topology entry in the TC_CONN table.

TKI: Leere/doppelte DialogLayoutName attributes

There is an attribute called "DialogLayoutName" which describes the name of the form. This maintenance checks for forms with an empty name but not 'NULL'. As well it checks for forms with identical names. There are known issues if a form has an empty name or the same name as another one. Normally the standard form does not have a name (value 'NULL'). If there are other forms recognized without a name or an empty name it might be shown instead but not wanted. This 1-Click-Maintenance identifies this forms. If you click on 'solve problems' empty names will be set to 'NULL'.  If there is more than one form with the same name, it will be renamed. It will be either 'Standard_{NR}' or 'name_{nr}'. {Nr} will be replaced by a sequence and name will be the existing name.

Known geometry errors and solution approaches (Oracle)

Error Cause Solution approach
ORA-13356 Geometry has duplicate snap points Edit the geometry and delete the duplicate snap points. The SQL statement for correct the snap points can be requested from TKI support if necessary.
ORA-13349 A polygon intersects itself Geometry should be re-digitized
ORA-13367 A polygon has an incorrect orientation The SQL statement for correct the orientation can be requested from TKI support if necessary.
Invalid geometry Geometry not supported for LineString A point is defined in a line geometry. The element can be deleted if necessary.
ORA-13011 The geometry is outside the value range. When the industry model was created, the maximum value was probably not increased by one place in the spatial configuration. The SQL statement for correct the range can be requested from TKI support if necessary.