How-To - ArcFM - Configure Feeder Manager 2.0 using GlobalIDs

Version 6

    The Feeder Manager 2.0 Configuration Guide uses ObjectIDs from the CircuitSourceID table to populate and maintain the following:

    1. The CircuitSourceID field on SubSource features (such as a Switch or Fuse). For example, on a Switch, if the user changes the SubSource field to "Yes," the following will occur:
      1. A new record will be created in the CircuitSourceID table to note the new SubSource;
      2. The ObjectID of the new record will be populated in the Switch's CircuitSourceID field.
    2. The SubfeederIDs field on all network features. The SubfeederIDs field is part of the set of Feeder Manager 2.0 fields (along with Feeder IDs, Energized Phases, etc.) that are dynamically joined to a feature class when it is opened in ArcMap (see below). You will not see these fields in ArcCatalog but will see them in the ArcFM Attribute Editor in ArcMap.

    distr.png

    *Note: If you populate the FacilityID field on the Switch, then the Subfeeder IDs of downstream features will list the FacilityID instead of the ObjectID.

     

    If you are using Replication and/or wish to keep track of your CircuitSources using GlobalIDs, the configuration instructions will deviate as follows:

    • Step 3: Create Feature Classes: On features that you wish to be modeled as SubSources (features such as protective or switchable devices), do not create the CircuitSourceID field with a Data Type of long integer. Instead, create a field called CircuitSourceGUID with a Data Type of guid.
    • Step 6: Assign Model Names:
      • CircuitSourceID: Do not assign the CIRCUITSOURCEID field model name to the ObjectID field. Instead, assign the CIRCUITSOURCEID field model name to the GlobalID field.
      • SubSources (such as DynamicProtectiveDevice, Fuse, Switch): Do not assign the CIRCUITSOURCEID field model names to the CircuitSourceID fields. Instead, assign the CIRCUITSOURCEGUID field model name to the CircuitSourceGUID field that you created above.
    • Step 9: Assign Autoupdaters: There is a known bug (MM54124) whereby the 'ArcFM Feeder SubSource Name' and 'ArcFM Feeder SubSource Level' autoupdaters are not available when just the CIRCUITSOURCEGUID field model name is assigned.  As a workaround, please perform the following:
      • temporarily assign the CIRCUITSOURCEID field model name to the CircuitSourceGUID field
      • assign the 'ArcFM Feeder SubSource Name' and 'ArcFM Feeder SubSource Level' autoupdaters per instructions
      • remove the he CIRCUITSOURCEID field model name from the CircuitSourceGUID field