Design Optimization - Update Engineering Tables

The ArcFM Solution installation sets up all engineering tables in a single database: ArcFM Solution\Support\EngAnalysisLookupTables.mdb.You may import the tables in this database into your own database. They are required for analysis tools as well as Design Optimization.

If you are configuring Designer for the first time or haven't configured the analysis tools in a prior release, you may import the engineering tables from this database into your geodatabase, then skip to the next step. If you've configured analysis tools in a prior release, you will already have some of these tables in your geodatabase. You will need to update some of the existing tables with new columns and add new tables to your geodatabase.

NOTE: Some of the fields in these tables require you to determine which CU favorites are used to replace graphic favorites when the design is completed. All favorites used with Design Optimization MUST have the Work Function field set explicitly to Install.

Add or Modify Columns to Existing Tables:

You will need to add columns to two existing tables. If you choose to import these tables from the sample database, note that any data in these tables or model names that have been previously assigned will be lost.

MMENG_TRANSFORMER

This table is used to specify types of transformers used by Design Optimization. The transformers represented here act as a list of "stock items" that are used in construction. Add the following column to this table:

DN_OPT_FAVORITE_NAME: This column specifies the favorite to replace a transformer graphic upon completion. When the user completes an optimized design, the transformer graphics are replaced with the favorite designated in this column. Enter the favorite name as it appears in the Favorites category on the CUs tab.

MMENG_CONDUCTOR_ELEC

This table specifies primary, secondary, and service conductor types available for construction. Only secondary and service conductor types are utilized by Design Optimization. Design Optimization allows a mixed use of conductor materials during optimization. Secondary circuits are built with optimal conductor types for each service delivery point. Therefore, multiple services connected to the same pedestal or transformer could potentially use different conductors types.

Modify the following column in this table:

COST_PER_UNIT_LENGTH: Ensure all values in this field are greater than zero.

Add the following columns to this table:

SECONDARY_FAVORITE_NAME: This column specifies the favorite to be used for a secondary conductor graphic. When the user completes an optimized design, the secondary conductor graphics are replaced with the favorite designated in this column.

SERVICE_FAVORITE_NAME: This column specifies the favorite to be used for a service conductor graphic. When the user completes an optimized design, the service conductor graphics are replaced with the favorite designated in this column.

PRIMARY_FAVORITE_NAME: This column is not currently used by Design Optimization.

Add New Tables

Add the following tables to your geodatabase. They may be exported from EngAnalysisLookupTables.mdb.

MMENG_PEDESTAL: This table specifies the types of pedestals used by Design Optimization. The pedestals represented here act as "stock items" that are used in construction.

MMENG_LOADPROFILES: This table catalogs the various load profiles to be considered for the design. Each row provides a description of a typical consumer load type for the utility. Administrators can configure various types of loads here. Each load profile can specify a coincidence curve that allows the optimizer to account for diversified load demand.

MMENG_COINCIDENCE_CURVES: This table allows the configuration of load coincidence curve for services connected at a transformer. Note that a load profile references a particular curve, as specified in the MMENG_LOADPROFILES table.

Once you've added the necessary engineering tables and columns, they will need to be populated. There are many ways to add data to these tables. For example: Access, Enterprise Manager, Toad.

NOTE: When entering a favorite name value, ensure the favorite exists in your geodatabase.
QR code for this page

Was this helpful?