Collapse All Expand All

Version: 10.2.1b and 10.2.1b SP1

Resource Center Home

The topic describes the process of upgrading your current Network Adapter implementation (Classic Implementation 1, Windmil) to the Standalone Implementation 2 (Windmil). The process involves modifying an XML configuration file according to your current configuration. The XML configuration file enables the standalone Network Adapter to replace your classic implementation.

Download the following file and open it in a text editor that provides XML formatting, such as Notepad++.

NetworkAdapter.exe.config

The following sections describe the areas you need to focus on in order make the transition from your classic Network Adapter implementation to a stand-along implementation. Adjust the new, standalone config file you just downloaded according to the configuration specified in the classic Network Adapter Options window (available from the MultiSpeak toolbar). Use the configuration section named MinervilleToMultiSpeakForWindMil.

Geometric Network Name and Densification

Change the GeometricNetworkName to the name of your geometric network.

	Copy Code
<add name="MinervilleToMultiSpeakForWindMil" GeometricNetworkName="ElectGeomNetwork" GlobalIDs="false" DensifyCurves="false" MaxAngleDeviation="10.0">

If you want to use the DensifyCurves function, which splines your curves with line segments, set it to true. If necessary, adjust the MaxAngleDeviation.

Connection Settings

Uncomment this section and change it to accommodate your server.

	Copy Code
<SdeElement Server="optimus" Instance="sde:oracle11g:/;local=orca.optimus" 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" /> </SdeElement>

Field Model Names

Field model names are not optional in the standalone Windmil implementation. Make sure you assign field model names in the <FieldModelNames> section of your config file.

Optional Configurations

The Validate Phase and Validate Voltage sections of your configuration file are optional in a standalone Network Adapter implementation for Windmil.

Set Export Database

1. The Default attribute in the NetworkAdapterSection tag determines the database from which data is exported. You add connection information for multiple databases in this configuration file. The Default value indicates the connection to be used. Follow steps 3-6 for each database to configure.

        <NetworkAdapterSection Default="ConfigName">

Use the <add> tag to specify a geodatabase. Provide information for the following attributes of the <add> tag:

• Name: Use this attribute to specify a name for the connection. You can name the connection anything you like.
• GeometricNetworkName: The name of the electric geometric network in the geodatabase. Be sure to include the prefix (e.g., ARCFM.ElecGeomNetwork).

        <add name="ConfigName" GeometricNetworkName="ARCFM.ElecGeomNetwork" GlobalIDs="false">

2. Under the <add> tag is the <SdeElement> tag. Use the attributes in this tag to set the geodatabase connection information.

• Server: Enter the name of the server.
• Instance: Enter the instance.
• Database: This attribute is necessary only for SQLServer connections or Access databases. For SQLServer, enter the database. For Access, enter the path to the geodatabase. You can enter a file geodatabase (.gdb) or a personal geodatabase (.mdb)
• Version: Enter the version to export feeders.
• User: Enter the user name to be used to log in.
• Password: Enter the password that corresponds with the user name. This password is encrypted when you run the Network Adapter executable file.

         <SdeElement Server="hispania" Instance="5152" Version="SDE.DEFAULT" User="arcfm" Password="*#Kk%(RJcJBiLokdw=">

3. Change the WorkspaceFactory element only if you are using an Access database. The QualifiedTypeName attribute specifies the type of workspace. For Oracle and SQLServer this value should be as shown in the example below.

• Oracle and SQL Server:

         <WorkspaceFactory QualifiedTypeName="Esri.ArcGIS.DataSourcesGDB.SdeWorkspaceFactoryClass, 
                Esri.ArcGIS.DataSourcesGDB, Version=10.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86" />

• Access Geodatabases:

         <WorkspaceFactory QualifiedTypeName="Esri.ArcGIS.DataSourcesGDB.AccessWorkspaceFactoryClass, 
                Esri.ArcGIS.DataSourcesGDB, Version=10.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86" />

4. The ModelNames section allows you to set the model names and the classes or fields to which they should be assigned. When exporting, Network Adapter will export the classes, attributes and relationships to which the specified model names are assigned. The ReverseRelationshipModelNames section holds model names assigned to unusual relationship situations. For example, a switching facility is the origin of a 1-M relationship class, while normally a network device would be the origin.
   
   The example XML below depicts the NetworkAdapter.exe.config default settings.
   
   The FeatureIDFieldModelName value determines which field is used to display feature information in the NetworkAdapter.exe results window. If this value is not set, the feature's ObjectID is used. By default, this value is set to FACILITYID.

   Copy Code

   <ModelNames FeatureIDFieldModelName="FACILITYID"> <ClassModelNames> <add name="MULTISPEAKCLASS"></add> </ClassModelNames> <FieldModelNames> <add name="MULTISPEAKFIELD"></add> <add name="MULTISPEAKEXTENSION"></add> <add name="MULTISPEAKEQUIPMENT"></add> </FieldModelNames> <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 model names in the ElectricModelNames section are used by phase and voltage validation. Do not modify these model names.

5. Ensure you are using the correct style sheet for your database. Uncomment the appropriate rule for your data model.

• The MultiSpeak data model uses NetAdapterMsp_Windmil.xsl.
• The Electric Distribution data model uses NetAdapterElecDistToMsp_Windmil.xsl.

The default location for all style sheets is: C:\Program Files (x86)\Miner and Miner\ArcFM Solution\Bin\Style Sheets

 

 

---

Send Comment to ArcFMdocumentation@schneider-electric.com