What's New in 10.0.1 SP1?

Version 6

    This page outlines what's new in the current release. If you are upgrading from more than one release prior, it is important to review all What's New pages for each release between your original release and the release to which you are upgrading. On these pages, look for required changes to custom code as well as interfaces that may have become obsolete.



    This page outlines the upgrade steps for various ArcFM Solution applications. These are basic required upgrades and do not include configuration for new tools. If you are skipping release versions (e.g., upgrading from 9.3.1 to 10.0.1), note the following:

    • DO NOT install each release in between. Only install the version to which you're upgrading.
    • DO review the upgrade steps for each release in between the original version and the one to which you're upgrading. Perform any additional upgrade steps outlined on these pages (e.g., recommended Esri patches, Responder upgrade steps, Process Framework database upgrades, etc.).
    • DO run the Create/Update ArcFM Solution System Tables tool only once. There's no need to run it multiple times.
    • DO run the Upgrade ArcFM Solution Database tool only once. There's no need to run it multiple times.
    • DO review the What's New page for each release in between. These pages will outline the new functionality available to you.
    • DO review the Migration pages for each release in between. These pages will let you know if you need to compile custom code.


    Migrate Custom Code

    This section provides a list of API changes for 10.0.1 SP1. Be sure to review the API changes and perform any migration steps for releases between your original version and the one to which you are upgrading.



    What's New in Responder?

    • The Responder team has made a number of server-side enhancements to improve data throughput as well as end user performance.
    • Responder Explorer offers a new report called Customer Count by Feeder. This report is available in the Generate Reports window. It provides a list of feeders with the number of customers on each.
    • In Responder Explorer, the grid now displays an Address field for incidents and devices. This information is available on incidents, devices, features and hazards. The address in this field is determined by specific criteria. This field is populated on a specific set of rules, but can be edited manually as well using the Create and Edit windows.
    • The Time of Outage field on the Edit Incident window may be edited in certain situations. This new functionality requires no additional configuration. See the Edit Incident in Responder Explorer page in the Using Guide for details.
    • Responder tools better support multi-feed situations. Note that a couple tools (e.g., consolidate, move upstream) warn the user if the upstream incident creation finds multiple paths and can't choose one specific location for the creation.
    • Responder now supports the ability to manually create SCADA incidents.
    • The Responder team has made a number of client-requested enhancements to the web application, including:
      • The user receives notification after cancelling a call.
      • Remarks from the dispatcher are visible on the web form when the customer is part of an existing incident.
      • The user can search for a customer using a meter number.
      • An administrator can set the default settings for the Trouble, Hazard and Cause fields.
      • When creating a switch order request, the user now has the option to skip the second and third screens.
      • All Estimated Times of Restoration (ETRs) in the system are visible on the Dashboard. These may optionally be removed.
    • The Responder Configuration Guide now includes steps to use Definition Queries to create the Loadpoints and Calls layers.
    • Responder includes additional caching to improve the performances of its services. With this configuration, Responder will open each feature class in the geometric network when the services start up and hold references to the open feature classes for the life of the process. This minimizes schema locks to improve performance. This enhancement is enabled by default.
    • Typically Responder Explorer accesses Data Services when starting up. However, if all instances of Data Services are busy, Responder Explorer could time out. A new optional configuration allows Responder Explorer to access Query Services or Data Services during startup.


    What's New in Smart Operations?

    • You may choose to integrate Responder with AMI and process meter events in Responder Explorer. The steps to configure Responder to use the Smart Grid Integration Framework to process AMI events are documented in the Smart Operations Solution section.


    What's New in Network Adapter?

    • The stand-alone version of Network Adapter now supports phase changing tie switches. These switches will be included in the export along with both feeders to which they connect.


    What's New in ArcFM Desktop?


    Fiber Manager

    • Fiber Manager offers directional tracing, which limits trace results to the one direction you select instead of tracing all possible directions.
    • The Connection Manager includes a Connection Viewer. The Connection Viewer allows the user to view fiber connections but not edit or create them. The Connection Viewer is displayed if you select the Connection Manager without starting an editing session.


    What's New in ArcFM Server?

    Several enhancements have been added to the ArcFM Server REST API.

    • The REST API now includes a Get Network EID tool that allows you to retrieve EID values for features.
    • The Gas and Water trace tools now include parameters for Valve Isolation traces. These parameters include excludedValves, includedValves, sqeezeOffs, and temporarySources. These parameters take EID values of the features you want to specify. Use the Get Network EID tool to retrieve these values.
    • The trace tools (Electric, Gas, and Water) and Locate tool include a parameter for the spatial reference. Use this parameter to specify the spatial reference used to view the results. If you do not specify a spatial reference, the results are displayed using the spatial reference in the MXD used by the map service.