ArcFM Desktop Developer Guide
Notes for MilSoft Users
The XML for phase merges contains a fake node section that represents the junction at which the phases merge. This fake node section contains multiple parent section IDs. The fake node section becomes the parent of the downstream feature.
Milsoft requires both a symbol coordinate and a location coordinate. The symbol coordinate is placed under the extension for each device.
A fake node section is inserted into the XML for each feeder. This provides support for feeder bays on the substation.
Milsoft models both sides of a switch. For every switch in the GIS model, there are two switches in Milsoft's model. Milsoft creates switch partners during the import whenever the MultiSpeak XML contains only one switch. The partner switches created by Milsoft have the same ID as the exported feature, with "-B" at the end.
There are two cases in which Network Adapter exports switch partners (before they are added upon import): open switches and tie switches. For open switches, Network Adapter duplicates the switch during export, adds "-B" to the ID string, and sets the partner and parentSectionID properties of each device appropriately. For tie switches, if only one feeder is exported, only one of the switch partners is exported with the MultiSpeak XML. If both feeders are exported simultaneously, then both switch partners are exported to the MultiSpeak XML.
For a closed switch, Network Adapter does not duplicate the device during export and allows Milsoft to duplicate it during import.
Windmil does not provide a place to store load data on transformer elements. Therefore, it is stored on the immediate upstream circuit element.
