Configure Dynamic Spec Assignment (Optional)

As stated in the previous topic, this step might be optional depending on the needs of your ADMS and OMS integrations.

A “spec” is a term that describes the electrical specifications of a component, which are required for calculations and data fidelity.

The spec ID is not stored as an attribute in the GIS features. If it were stored in the feature itself, there is a chance it would become out of sync with the feature as GIS edits are made over time. Further, it is difficult for an administrator to assign the ID to every feature in the GIS.

Instead, the spec ID is assigned “on the fly” as the design components are extracted from the GIS and brought into the design via the Edge service. In that manner, the ID is informed by the most up-to-date attributes for the GIS features. Further, it is much easier to let the service assign the ID. Finally, it is easier to maintain the system with future updates, as you do not have to go back and edit features’ spec IDs in the GIS.

But, how does the application know which spec ID to assign? You supply the “rules” by mapping attribute fields to spec IDs in an Excel table that is uploaded to Solution Center, where you inform the application which GIS fields to use when it assigns the spec ID.

This information is condensed into a single cell in the Catalog Export or Import Excel table:

RATEDKVA:15,HIGHSIDEVOLTAGE:12.5,LOWSIDEVOLTAGE:120/240,HIGHSIDECONFIGURATION:LG,LOWSIDECONFIGURATION:SP,PHASEDESIGNATION:1|2|4

Finally, that combination of attributes receives a spec ID in GUID format. As features are brought into the Geodatabase Regions (GRR), any transformer (in this example) that meets the above criteria receives that spec ID. Any transformer that does not would then be compared to other attribute combinations in the Catalog Export or Import Excel table. There would likely be several different combinations of attributes that inform an ID, and transformers would continue to be categorized by the service. Configuring the attribute combinations occurs in an Excel table that is uploaded to Solution Center.

Default Spec ID

As stated above, the application continues to compare the transformers (in this example) to the known spec criteria. But, if it cannot find a match, you can provide a generic or default spec ID. This should be the most generic set of attributes in order to act as a “bucket” to contain unmatched features. You should create a default spec ID for each component type. It should be the last spec per component type (in other words, at the end of all transformer specs should be the generic transformer spec, and at the end of all conductor specs should be the generic conductor spec, etc.).