Version: 10.2.1c and 10.2.1c SP3 |
Smart Grid Applications Overview > Network Adapter > Network Adapter for Multispeak > Network Adapter - Configuration File |
Most of the Network Adapter-DMS configuration is done in the NetworkAdapter.exe.config file. You will also need to assign some model names in the geodatabase to specify the classes and attributes to be exported.
<NetworkAdapterSection Default="ConfigName">
Use the <add> tag to specify a geodatabase. Provide information for the following attributes of the <add> tag:
<add name="ConfigName" GeometricNetworkName="ARCFM.ElecGeomNetwork" GlobalIDs="false">
GlobalIDs: Any time the GlobalIDs value changes, you will need to repopulate the mapping tables. First truncate the tables owned by the SMARTGRID owner, then export with Network Adapter with the appropriate pipeline rules enabled. GlobalIDs and Data: If the GlobalIDs value is enabled, then every feature class in the network must have a populated GlobalID field. If this field doesn't exist on each feature class or is not populated, you will experience data errors when exporting. |
<SdeElement Server="hispania" Instance="5152" Version="SDE.DEFAULT" User="arcfm" Password="*#Kk%(RJcJBiLokdw=">
<WorkspaceFactory QualifiedTypeName="Esri.ArcGIS.DataSourcesGDB.SdeWorkspaceFactoryClass, Esri.ArcGIS.DataSourcesGDB, Version=10.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86" />
<WorkspaceFactory QualifiedTypeName="Esri.ArcGIS.DataSourcesGDB.AccessWorkspaceFactoryClass, Esri.ArcGIS.DataSourcesGDB, Version=10.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86" />
Copy Code <ModelNames FeatureIDFieldModelName="FACILITYID"> <ClassModelNames> <add name="MULTISPEAKCLASS"></add> </ClassModelNames> <FieldModelNames> <add name="MULTISPEAKFIELD"></add> <add name="MULTISPEAKEXTENSION"></add> <add name="MULTISPEAKEQUIPMENT"></add> <add name="HIGHSIDECONFIGURATION"></add> <add name="LOWSIDECONFIGURATION"></add> <add name="FEEDERID"></add> <add name="SUBSTATIONID"></add> <add name="LOWSIDEVOLTAGE"></add> <add name="OPERATINGVOLTAGE"></add> <add name="SCADACONTROLID"></add> <add name="FACILITYID"></add> <add name="MEASUREDLENGTH"></add> <add name="FAULTINDICATORDIRECTION"></add> <add name="TAPCHANGEREQUIPMENT"></add> <add name="TAPCHANGEREQUIPMENT1"></add> <add name="TAPCHANGEREQUIPMENT2"></add> <add name="TAPCHANGEREQUIPMENT3"></add> <add name="TAPCHANGEREQUIPMENT4"></add> </FieldModelNames> <RelationshipModelNames> <add name="MULTISPEAKCLASS"></add> </RelationshipModelNames> <ReverseRelationshipModelNames> <add name="RELATEDSUBSTATION"></add> </ReverseRelationshipModelNames> <ElectricModelNames LowSideVoltageFieldModelName="LOWSIDEVOLTAGE" OperatingVoltageFieldModelName="OPERATINGVOLTAGE" PhaseDesignationFieldModelName="PHASEDESIGNATION"> </ElectricModelNames> </ModelNames>
Using the example above, Network Adapter will export all classes that have the MULTISPEAKCLASS model name assigned. For each exported class, Network Adapter will export the fields with the model names specified by the Field Model Names section. The MULTISPEAKCLASS model name should be assigned to all classes on the Supported Attributes table.
Assign the MULTISPEAKFIELD model name to any field to include in the export. This model name should be assigned to all fields in the Supported Attributes table.
The MULTISPEAKEXTENSION model name can be used to export a field that doesn’t appear in the MultiSpeak data model. Assign the MULTISPEAKEQUIPMENT model name to the field that represents the EquipmentID. The LOWSIDEVOLTAGE and OPERATINGVOLTAGE model names are necessary for the Voltage Validation rule. If you don’t want to validate voltage, then these fields do not need to be included in the export.
The following field model names are necessary in order for the XML transformation to occur properly: MULTISPEAKEXTENSION, MULTISPEAKEQUIPMENT, HIGHSIDECONFIGURATION, LOWSIDECONFIGURATION.
The model names in the ElectricModelNames section are used by phase and voltage validation. Do not modify these model names.
<endpoint address="http://172.18.226.196
:8080/StaticDataService" binding="basicHttpBinding"
bindingConfiguration="BasicHttpBinding_IStaticDataService"
contract="IStaticDataService" name="BasicHttpBinding_IStaticDataService" />