ArcFM Desktop Developer Guide
Configure Geodatabase for MultiSpeak
Version: 10.2.1a |
The field names and table names shown below are NOT case sensitive.
Network Adapter also requires the following configurations. It is recommended that you perform the following configurations before continuing with your Network Adapter implementation. Step-by-step procedures for performing these configurations are available in the Configuring ArcFM Solution online documentation.
To configure Network Adapter to integrate with MultiSpeak-compliant analysis tools, the following model names must be assigned.
The MULTISPEAKEAEXPORT model name must be assigned to all classes that should be exported. You may assign MULTISPEAKEAEXPORT to the specific fields you wish to export as well. If the model name is assigned only at the class level, all fields are exported (assuming the correct option is set). It is recommended that you assign the field model name as well to increase performance.
The export also depends on the options set using the Options button on the Network Adapter/MultiSpeak toolbar. By default, no field model names are assigned. To export only specific fields, you must set the option to export field information as well as assign the field model name. Information about setting the MultiSpeak Options in Network Adapter are available in the Using Network Adapter online documentation.
Default Junctions
The default junction class is created when you build the electric geometric network. This feature class may be included in your selected set, but it must first be configured. You must also assign the MULTISPEAKEAEXPORT model name to this class, otherwise it will not be exported. Include default junctions in your selected set if you wish to symbolize results for complex edges.
If you wish to omit the default junction class from your selected set, do not assign the MULTISPEAKEAEXPORT model name.
LoadCase Table
We recommend creating this table as a view in Oracle or SQL Server instead of a table, using the SQL statement provided below. In Access, it must be a table, and it must be populated with one record for each load case. For example, if you have two load cases, 'Winter Peak' and 'Summer Peak', this table would only have two rows, one for each load case name.
Object Class Model Names: MSPLOADCASE, ARCFMSYSTEMTABLE
Field Model Names:
Field Name
Field Model Name
FacilityID
MSPLOADFOREIGNKEY
LoadName
MSPLOADCASE
PhaseCD
PHASEDESIGNATION
KWA
MSPKWA
KWB
MSPKWB
KWC
MSPKWC
KVARA
MSPKVARA
KVARB
MSPKVARB
KVARC
MSPKVARC
The MSPLOADFOREIGNKEY field model name indicates a unique ID for network features that have related load data. This field is used as a key between the LoadCase table and the network feature class that it is related to (typically TransformerBank or ServiceLocation), and it should be assigned to the key field in both the LoadCase table and the feature class. The relationship between the feature class and the LoadCase table is 1 to many. You do not need to build a relationship class between the LoadCase table and the feature class; the relationship is created in memory during the export.
The MSPLOADCASE field model name denotes the name of the load case. This field is used to distinguish between multiple load values relating to the same feature. For example, you may store both winter peak and summer peak load values in the LoadCase table. You can do this by assigning a different load name to each record. "Winter Peak", and "Summer Peak", for example.
Information about class model names and field model names is available in the Appendix of the Configuring ArcFM Solution online documentation.
TransformerBank Feature Class
Object Class Model Names: MSPLOADPOINT
Field Model Names:
Field Name
Field Model Name
FacilityID
MSPLOADFOREIGNKEY
ServiceLocation Feature Class
Object Class Model Names: MSPLOADPOINT
Field Model Names:
Field Name
Field Model Name
FacilityID
MSPLOADFOREIGNKEY
LoadNames
In Access geodatabases, LoadNames is a table. However, in an SDE database, we recommend that LoadNames be a View. The LoadNames View must be created using the unique LoadName values in the LoadCase table. When creating a view, you must be logged on as the owner of the schema in which the view will be placed. Below is an example of the SQL command used to create the View.
Create View loadnames_v as Select Distinct LoadName from ArcFM8.LoadCase
Object Class Model Names: MSPLOADNAMES
Field Model Names:
Field Name
Field Model Name
LoadName
MSPLOADCASE
If neither version of Feeder Manager is configured
If Feeder Manager is not implemented (the trace weight field is not found), the following model names are required:
Class Model Names: SOURCE, TRANSFORMER
Field Model Names: FEEDERID, FEEDERID2 (if Feeder Manager 1.0 is configured), PHASEDESIGNATION, NORMALPOSITION_A, NORMALPOSITION_B,
NORMALPOSITION_C, OPERATINGVOLTAGE
All of these model names are interpreted in exactly the same way as Feeder Manager. For example, the Normal Position field model names are only assigned to switchable devices. If the Normal Position model names are not assigned to a class, MMSelectionAnalysisAPI assumes the class is not a switch or protective device. Similarly the OPERATINGVOLTAGE field model name is only assigned to conductors. (See the Configuring ArcFM Solution online help in ArcCatalog for information about configuring Feeder Manager.)
