When to create associations?

mshanaghan

At what point in a utility network implementation do you create associations between features, eg. make a substation a container which contains transformers, switches, and regulators?

I am currently mapping fields using a data loading workspace. As I understand it, my next step will be to load data into the asset package using the "Load data using workspace" tool. Then I will apply the asset package to a geodatabase using the "asset package to geodatabase" tool.

Should associations be set up before I run the "asset package to geodatabase" tool? 

RobertKrisher

Performance

From a performance standpoint, putting the associations in the asset package is the fastest way to load the associations for features contained in the asset package.

You can always bulk load them later using the import associations tools, but if you do this after your data has been versioned it will be slower.

Creating Associations

You can create associations inside the asset package (based on spatial proximity) using the Create Association Records tool found in the UN Package Tools toolbox. You can also create your own tools or processes to load the C_Associations table in the asset package if you want.

You can also create your own CSV file you can bulk load/import associations using the products Import Associations tool.

You can create associations for newly created features by either using editing templates that contain associations (typically preset templates).

You can also dynamically generate associations when features are created/updated/deleted using attribute rules.