Load cases are created by exporting data from the geodatabase into the Network Adapter database. When the user clicks the Get Load Case button, he is prompted to enter a load date. Network Adapter uses this load date to query the Transformer_Load_CYMDIST or Transformer_Load_ElecSolver table in the geodatabase and add the information to the LoadCase_Transformer table in the Network Adapter database. Network Adapter automatically designates all load case tables as dirty during a standard feature export. A load case table is designated as clean after it is exported or after new data is imported to the table. During configuration, you will assign the "ArcFM Update Network Adapter Table" autoupdater to the load case tables. This autoupdater notifies Network Adapter that a table is dirty when it has been edited. Use the IMMXMLData interface to export data from the geodatabase. To define a load case export, populate the TestCaseName property with "LoadCase" in the export properties. Network Adapter uses the load case name to find the load case table. If the table is dirty (edited since the last load case export or import), the load case will be exported from this table. Network Adapter does not export the load case if the table is found to be clean. Utilizing load cases requires some configuration. |
|
There are methods the implementer can use to assign loads in the CYMDIST API. The loads can be appended to features in the exported XML before the XML is imported to the CYMDIST through IMMXMLData::ImportDataFromDOM. In addition, the implementer can assign loads to features already in CYMDIST memory using the IMMCymdistAPI::ApplyTestCase method.
The Implementation should provide means for the user to select a default load case. For example, the implementer can provide a user interface for selecting a default load case based on date, time, and other factors. The Implementation imports the user-selected default load case to the Vendor API to be considered in the analysis. If the Implementation imports the default load case also to the Analysis API, the user can edit the load case with the Attribute Editor.
The implementation should provide means for the user to select a default load case. For example, the implementer can provide a user interface for selecting a default load case based on date, time, and other factors. The user-selected default load case is imported to the Electric Solver API to be considered in the analysis. If the default load case is imported to the Analysis API, the user can edit the load case with the Attribute Editor.
The Electric Solver API allows the implementation to assign loads to devices. If loads are assigned to a device, the Electric Solver API automatically assigns this load to the downstream end of the section where the device resides. The implementer assigns loads to features already in Solver memory using the IMMElecSolverAPI::ApplyTestCase method.
For CYMDIST and SynerGEE exports, load case data may be exported to a personal geodatabase, where the data may be modified to create 'what if' scenarios. Load case data is then exported into an XML which may be imported into your analysis engine or its Vendor API.
The Load Data page addresses XML exports for load data. This page focuses on exports for load flow analysis.
Use the Analysis API to export all features and attributes required for analysis. Additional features may be required for later use in results display. For example, you may be required to display results for conductors at the downstream junction feature of each conductor. Thus, junction features are necessary for results display and must be included in the export.