You can use model driven attributes to provide a consistent and smart way of data acquisition. Using model tables, you constrain attributes based on other attributes. These attributes are called model driven.
Example: To use a model table for diameter and material
The following instructions show the concept of model tables. For example, in Gas, you use the Pipe Model table, to acquire Pipe attributes.
To use a model table for data acquisition
The Pipe Model form consists of two sections: At the top is the filter section for the model attributes. Use the horizontal scroll bar in the middle of the form to view all attributes. The lower section displays the models (model table records) that match the current feature. For example, if not all model related attributes of the main feature are filled, several models would be applicable.
Alternatively, you select a model from the model list. In the Pipe form, on the General tab, select a model from the list. The list displays the Model Name (MODEL_NAME). If no model name is assigned, the list shows an empty entry. If the model table does not contain the attribute MODEL_NAME, the value of the VALUE attribute is shown. If no attribute VALUE is available, the list shows the FID.
To assign a model table to an existing feature class
You can use any attribute feature class as model table. If the model feature class contains attributes that are not in the main feature class, you can optionally add these attributes.
In the parent feature class form, the model table can be accessed using the Model Selector. Use the Form Designer to add the Model Selector control.
To add the Model Selector.
Older versions of the enterprise industry model used model tables named <name>_MODEL. When you open an industry model that has the old model table structure, the system updates existing model tables, so they support the new concept of model driven attributes.
The data structure update performs the following steps.
The model feature class is still being used, according to the new concept. However the model attributes are now stored in the main feature class, and you use the model table to support data acquisition.