Before beginning a Network Adapter implementation, there are several things to first consider.
- Network Adapter relies heavily upon the integrity of your data. It is critical to begin your Network Adapter implementation with good data. The Data Dependencies page discusses tools that can help validate your data and as well as specific data problems that hinder Network Adapter. Remember, incorrect data only generates incorrect analysis results.
- Network Adapter exports feeder data from the geodatabase and imports it into a third-party analysis tool such as a MultiSpeak-compliant analysis engine such as Milsoft. These third-party tools must be installed and tested before implementing Network Adapter.
- 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.
- Basic ArcFM Configuration.
- Feeder Manager 1.0 or 2.0. For help determining which version of Feeder Manager is best for your needs, see Which Feeder Manager Should I Use?.
- Determine how you want to use Network Adapter and select a scope of implementation.
- Choose an engineering analysis engine and obtain the appropriate licensing. Network Adapter supports the MultiSpeak compliant analysis engines (Milsoft).
- If invalid or incomplete attribute values exist in your network before this implementation, they will remain. This inaccurate data may be exported into your third-party engineering analysis engine.
- Each feature in your geodatabase must map to a feature in the Equipment database using an Equipment ID. Before implementation, you may wish to determine how Equipment IDs will be assigned and maintained. Below are some options. Equipment IDs and the Equipment database are discussed in detail in the section that corresponds to your engineering analysis engine.
- Add Equipment ID fields to the database and maintain them by manually editing.
- Add Equipment ID fields and create autoupdaters to maintain them.
- Assign Equipment IDs programmatically during the implementation using key attribute values (e.g., rated kVA or conductor size).
Why use standalone implementation?
Here are some reasons to upgrade from classic to standalone:
- Better performance.
- The export is processed one feeder at a time, which means the demands on memory aren't as severe. Classic NA was driven by a selection set in ArcMap, and users typically grabbed an entire substation at a time which meant they encountered severe performance degradation as their DOM document was written out to the pagefile.
- It only requires an ArcGIS Engine license.
- You can schedule exports with the task scheduler using the command line interface.
- It's easier to customize.
- Use your customized DTDs if you need to change the mapping.
