ArcFM Desktop Developer Guide
Supported Attributes for MultiSpeak Loads
Load case data is stored in the geodatabase in the LoadCase and Load Names tables. These tables are included in the sample geodatabase installed with ArcFM Solution. You may export these tables from the sample data and import them into your geodatabase. You may also create the tables in your geodatabase. The MultiSpeak LoadCase table contains a row for every feature in a load case. You may have multiple load cases which are differentiated by load name. The LoadNames table contains one row for every individual load case.
The MultiSpeak LoadCase table differs from the load case tables for CYMDIST and SynerGEE in that it does not have a pre-determined set of supported attributes. The features and attributes included in the LoadCase table are determined by model names. The tables below depict the recommended configuration for the LoadCase and LoadNames tables.
If you choose to retrieve load case data from another source, a load table is not necessary in the geodatabase.
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', the LoadNames table would only have two rows, one for each load case name. The LoadCase table would include one record for each feature included in both load cases.
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.
Object Class Model Names: MSPLOADPOINT
Field Model Names:
Field Name
Field Model Name
FacilityID
MSPLOADFOREIGNKEY
Object Class Model Names: MSPLOADPOINT
Field Model Names:
Field Name
Field Model Name
FacilityID
MSPLOADFOREIGNKEY
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
