Send Comment to ArcFMdocumentation@schneider-electric.com
Version: 10.2.1d and 10.2.1d SP2 |
| Overhead Design Analysis > Step by Step Guide |
A complete customized configuration of Overhead Design Analysis (OHDA) is accomplished in four major steps.
Unless you plan to use OHDA as a stand-alone application, you will need to configure your geodatabase for integration with ArcMap and Designer. After completing this step, you will be able to export poles, cables, and assemblies from ArcMap with a Designer license to OHDA. This step is technically optional, but if you attempt to export these items without configuring the geodatabase first, OHDA will replace the items imported with placeholder equipment. You will then need to manually edit any placeholder equipment before OHDA will analyze the scenario.
OHDA ships with NESC standards and construction grades as its default. For many, these standards are sufficient for their designs. If you have standards and construction grades other than NESC (e.g., GO95 or CSA) that you must meet, then you will need to manually edit the StandardsAndConstructionGrades XML file. Follow the link below for the details of this file.
Once your database is setup, you will need to create matching elements for OHDA to consume. If the information you create here does not match the geodatabase, OHDA will create placeholder design elements that you will need to manually edit before OHDA can analyze the scenario.
If you are not integrating OHDA with ArcGIS, you will still need to simulate the actual equipment that you or your team will use in your design. As with any analysis tool, the exactness of calculations will depend in large part on the quality of data you create.
You will need a basic understanding of XML file structure and a simple text editor (like Notepad) to configure the equipment.
OHDA ships with several of the most common wood utility pole specifications. If these poles do not match the materials you will be working with in the field, then you will need to create an XML file to represent those materials.
If you are integrating with Designer, then creating a GisMatchingString element is essential in importing poles from ArcMap. OHDA will use this element to match your XML file to the feature you are importing. If you are not integrating, you will still need to create XML files to supply the details of the poles in your scenario to get the most accurate analysis possible.
Like other materials in OHDA, assemblies are represented with XML files. Because of their complexity, however, the Assembly Creator tool is included with OHDA. Using Assembly Creator, you are able to visually create a comprehensive library of complex assemblies that mirrors the assemblies used in the field. Once you save your work, Assembly Creator creates the XML files that define your assemblies.
You will need to represent cables used in your designs with XML files. Like other pieces of equipment, if you are integrating with ArcMap you will need to create a GIS matching string to have OHDA recognize the cables you import from ArcMap. If you're not integrating, you will still need to create XML files to supply details of the cables in your scenario to get the most accurate analysis possible.
Guy wires play a large role in the forces exerted on a pole and ultimately the entire scenario. As such, it's important to have an accurate representation of the material used in the field. As with other equipment, you will need to define the specifications of your guy wires using the XML format.
Having an accurate representation of the anchors you'll use in the field is important for a precise force analysis. Like other equipment, you will need to define the anchors you will be using with specifications in XML files for OHDA.
By default, OHDA observes NESC clearance rules. If you are in California, however, you may need to have the defaults set to GO95 standards. OHDA ships with a Clearance Rules tool that you can use to set relevant clearance rules for your scenario. Clearance rules between wires and surfaces are recorded in one file, with rules governing pin spacing regulations recorded in another. Follow the links below to set each file.