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. You do not need to install each release between, only follow the upgrade steps and review the What's New pages. The current release installer will provide all functionality enhancements since your original version.
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.
This section provides a list of API changes for 10.1.1. 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.
- Ensure that your hardware and software meet the ArcGIS system requirements. These requirements are available at http://support.esri.com/.
- Ensure that your hardware and software meet the ArcFM system requirements defined at the ArcFM Solution Supported Versions web page.
- A 10.1.1 license is required for all ArcFM Solution 10.1.1 products. You can request a license online, through email, or by calling 1-970-223-1888 extension 199.
- You must be running Esri's ArcGIS 10.1 Service Pack 1 release to install ArcFM Solution 10.1.1. You can find information on the service pack at Esri's support site.
What's New in ArcFM Desktop?
- Feeder Manager 2.0: The new version of Feeder Manager tracks feeder information in memory. Editing performance is far superior to that of Feeder Manager 1.0, and you can expect a substantially reduced number of version conflicts.
- You can now dock the Attribute Editor, as well as tab through its fields.
- The ArcFM Attribute Editor, Locator, and Identify tools now support multiple joins when there is a one-to-one or many-to-one relationship between the data in the layer's attribute table and the table containing the information you want to join.
- The ArcFM Attribute Editor contains additional support for joined data:
- In many scenarios, the ArcFM Attribute Editor displays joined data that contains a map relate.
- You can use it to edit joined data in the source table (the layer's attribute table, not the table containing the information you want to join).
- It now respects the attributes of joined data, including field order, visibility, and primary display fields.
- The ArcFM Attribute Editor now supports joining to data tables from multiple workspaces. You can join to non-ArcFM tables, as well as external sources such as spreadsheets and other geodatabases.
- You can now use a Windows-style calendar to enter dates in the ArcFM Attribute Editor, or simply type the date in its field.
- The ArcFM Locator's Stop button is more responsive and useful during large searches.
- A new Autoupdaters Browser tab in ArcCatalog displays class and field autoupdaters assigned to feature classes and tables. You can also use this new tab to search datasets for autoupdater assignments according to event.
- ArcFM tools, including Feeder Manager 1.0 and 2.0, now support the SplitWithUpdate method of splitting lines. Unlike the old Split method, which deleted the existing feature and created two new features in its place, SplitWithUpdate updates the shape of the existing feature and creates a new feature using the default attribute values for the feature class. Furthermore, the ESRI_SPLITWITHUPDATE class model name is now obsolete; it has no effect on anything. Note that ArcFM does not support the use of Esri's Split command (which is different from Esri's Split tool) option to split Into Equal Parts. If you use this particular split command, related objects are not correctly maintained.
- This release includes a fix for GASNONTRACEABLE not being respected for gas junction features (MM51416). If an object is marked as nontraceable, tracing through it is prevented.
- Added support for Esri's "Split with Update" feature.
- CU Filter tool can now perform a search on compatible units based on description.
- CU Filter tool can now perform a search on template favorites based on name.
- A Reverse Highlight tool to quickly find CUs you select on the map in the Design tab tree.
- Designer now automatically creates non-graphical CUs when you add them to the design.
- Four performance enhancement improvements:
- Designer now caches the CU library, the CU favorites, and graphics to increase speed when opening multiple designs.
- Workflow Manager no longer runs a full table scan of MM_Px_History during the open process resulting in a much faster opening time.
- Designer now uses more efficient SQL queries when writing Design data to the Process Framework database, which reduces the time it takes to save a design.
- Designer now uses optimized SQL queries and improved caching when reading records from MM_Px_Versions. Customers working with many versions will notice the largest performance increase.
- Added support for Esri's "Split with Update" feature.
Overhead Design Analysis
We're excited to introduce Overhead Design Analysis (OHDA) with the 10.1.1 release. OHDA gives you the ability to model the infrastructure of your overhead designs in a 3D space to examine and analyze all the variables that determine a safe design:
- Analysis of the sag and tension of your cables under different environmental conditions and loads.
- Verification that safe clearance distances are maintained between wires and whatever type of surface is below.
- Structural analysis of the force placed on poles to ensure a sound infrastructure.
- Evaluation of the effectiveness of guys and anchors in a design to safely counteract opposing forces placed on a pole.
- Accounting for safety and reduction factors to confirm a safe design.
- Wavepoint: A brand-new product for viewing your network over the web.
- Fiber Manager now automatically handles fiber availability attributes. Whenever you use Circuit Manager to add, delete, or heal a circuit, or use Connection Manager to change a circuit path, the affected fiber availability fields are automatically updated. This includes the attributes for number of available strands belonging to a fiber optic cable, as well as the availability attributes of individual strands. This new functionality requires circuit healing and availability to be be fully configured. Availability attributes belonging to existing circuit participants are not changed until one of the above operations takes place.
- Fiber optic cables' footstamp markings can be printed in different units, depending on the type of cable or the vendor. These footstamp units may be different than your map units. Fiber Manager now provides a way to specify the particular footstamp units on fiber optic cables and cable segments. This ensures correct cable length calculations when footstamps provide the source of cables' lengths. View the Upgrade to 10.1.1 topic for configuration details.
- You can now add one or more extra fields to fiber reports. Six new field model names, one for each report in Fiber Manager (except the glass report), allow you to choose which fields appear in which reports. Consequently, the FIBERCONNECTIONDISPLAYFIELD field model name is no longer used for reporting, but is still used to add extra columns to Connection Manager. For more information, refer to the configuration guide help topic titled Configure Fiber Manager Reports.
- Reverse the rack order of items in the patch panel connection report. Simply assign the REVERSEORDERCHILDREN class model name to your rack table.
- In order to avoid the generation of incorrect data, fiber optic cables whose length source is set to Footstamps, Documents/Field Notes, or OTDR Length are changed after a split. Each of the two linear features resulting from a split revert to a length source of GIS Length + Slack Loops. A message displays whenever this occurs. You can turn off this notification in the Fiber User Settings.
- Your feature and object classes can now contain alias names with spaces. To access your feature and object class properties, right click them in ArcCatalog and select Properties. You can make these changes on the General and Fields tabs.
- You can now run OTDR traces from splice points.
- A new checkbox in Conduit Manager Options lets you choose whether to include phase designation in cross section annotations.
- No new functionality was added for the 10.1.1 release.
- No new functionality was added for the 10.1.1 release.
- You can now use stand-alone Network Adapter for Windmil. This mean that you can turn off Feeder Manager 1.0 when you upgrade to Feeder Manager 2.0. For instructions about how to upgrade your classic Network Adapter implementation the stand-alone version, visit the Customization Guide topic called Upgrade Network Adapter from Classic to Stand-alone for Windmil.
- CYMDIST and SynerGEE implementations of Network Adapter are deprecated.
What's New in Responder?
- Responder now allows you to Place Jumpers as part of a new or existing confirmed/active incident. An incident may have multiple jumpers. These are line features that allow you to temporarily connect two electrical line features. Jumpers currently display on the map and in Responder Explorer, affect tracing, may restore outages, and may potentially cause outages upon removal.
- Responder Phase Swap allows you to backfeed from one phase to a different phase. There are restrictions on this ability; see the help topic for more information.
- The ArcFM Isolation Trace in ArcMap now functions correctly when Responder users change the Network State from Normal to Actual.
- You can now copy information from the Responder Explorer Incident, Calls and Devices grids. See the Responder Explorer topic for more information.
- A new Remarks field is available for Electric Devices. You can edit this field by Correcting the Phase/Time of the incident or by editing the incident.
- Responder Explorer and Archive Explorer now support the option to set the time format from 12-hour time (i.e., 4:15:35 PM) to 24-hour time (i.e., 16:15:35) by selecting Use 24-Hour Time Format from the Tools menus.
- You can now save a hazard, that was related to a call that is also related to an incident device, as its own new incident.
- Significant performance improvements were made regarding Opening, Executing, and Archiving Switch Orders.
- From the View menu in the Switch Order Editor, you can now display both the Summary and Comments for individual operations when selecting either View on Map or View Selected Steps on Map. View Selected Steps on Map option also allows you to highlight the selected steps in the Switch Order Editor on the map with a callout.
- The Show Multiple Responder Features tool and Show Single Responder Features tool now automatically filters the incidents/calls/devices grids associated with all selected features (i.e., incidents, electric features, location features, hazards, and load points) within the polygon. You can configure this functionality to act as previously created (see View All When Selecting From ArcMap for more information.)
- Responder Explorer also now includes an indicator of the number of tasks showing in your grid, based on the filter, versus all tasks.
- The Customer List and Planned Work Report has changed to include allowing you to run a trace from a selected set of devices, and filter by Phase and Network State.
- A new Open Calls option has been added to the Customer Service tab in the Responder Web Portal. You can view customers/calls that have been submitted and are currently open/active in the system.
- In Archive Explorer, the ASAI (Average Service Availability Index) and the L-BAR Index values are included when running Reliability Reports.
- The following configuration options have been added for 10.1.1. In order to utilize these options, you must follow the configuration steps:
- Show Callers on Customer Tab: Allows you to disable including customers on the Customers Tab in Responder Explorer that do not include loadpoints. (This is also a configuration option for Archive Explorer.)
- Move Fault Upstream Respecting Downstream Phasing: Allows you to set the default action so that only the phases that are already open on a downstream device are open on the upstream device, when moving the fault upstream.
- Notify Call Reprocess on Restore: You can configure Responder Explorer to display a notification when you restore an incident at a time earlier than that of the outage time on calls associated with that incident.
- Exclude Planned Switching Values from the Dashboard allows you to exclude customer counts associated with planned switching from the elements visible on the Dashboard.
- The following new QA/QC Rules have been created for Responder and would require configuration. See the Validation Rules help topic in the Appendix for more information:
- Phase Designation Mismatch
- Phase Designation Not Populated
- FeederID Not Populated
- Operating Voltage Mismatch
- Operating Voltage Increase
- This release includes the following new developer samples:
- Custom Crew Sort Order: Illustrates how to change the order Crew Members appear in drop-down lists (such as the Executed by field when restoring an incident).
- Delete History on Cancel: Illustrates how to set the automatic deletion of the associated history of incidents when they are canceled.
- Prevent Complete with No Cause: Illustrates how to prevent an incident from being marked as complete if the Cause field does not have a value.
What's New in ArcFM Server?
- Added support for query layers and ArcGIS Server 10.1 SP1.