ArcFM Solution: The Director's Cut

The Designer Migration Two-Step

From time to time you may need to change the name of a Designer database or even copy the entire database to another location, perhaps to create a new testing environment or as part of a hardware upgrade.

Ideally you would reconcile, post, and delete all existing designs before beginning the migration. For occasions when some designs must remain outstanding during a migration, ArcFM and Designer provide two data source wizards that together can repoint existing designs to the new data location.

As always before making any major database change, back up the database (and in this case the MM_WMS_DESIGNS table in particular).

1. ArcFM Data Source Wizard
   • Changes the data source for Stored Display layers, including Stored Displays associated with particular existing designs. If this tool is not run, any designs that have their own Stored Displays will upon opening display red exclamation marks in the Table of Contents Display tab, and will fail to display the missing data on the map.
   • Launch in ArcCatalog by right-clicking the database connection and choosing ArcFM Data Source Wizard.
2. Workflow Manager Data Source Wizard
   • Changes the data source for the design workspaces. If this tool is not run, any designs that have their own Stored Displays may display error messages indicating that the workspace was not found. 
   • Launch from the ArcFM installation folder, under ArcFM Solution\Bin\ WorkflowManagerDataSourceWizard.exe.

During each of these two processes you will browse to the new data source. This should be the source of the business data (electric/gas/water/fiber/etc.), not the process framework data.

When migrating a Designer database, run both wizards, starting with the ArcFM Data Source Wizard. When migrating an ArcFM-only database, you will only need to run the ArcFM Data Source wizard because sessions do not save workspace information.

Webcast Follow Up: Server, Staker, Express, and Designer

Following the What's New in ArcFM 9.3.1 webcast and in anticipation of the pending release of 9.3.1 SP1 slated for later this month, we've received a series of questions relating to product functionality and tasks. So, we'd like to take this opportunity to share these inquires with you (and their answers, of course).

ArcFM Server

Q: Is there any print functionality or export to PDF functionality in ArcFM Silverlight Viewer?
A: Not yet. However, printing is one of our highest priorities for the next release.

Q: Are the Silverlight Toolkit and the ArcFM Silverlight Viewer product in the current 9.3.1 release or the pending 9.3.1 SP1 release? 
A: Both are officially part of the 9.3.1 release and in so are available for download by registered users on our web site.

Q: Can you search on a field in related data at 9.3.1?
A: Yes. And furthermore, which specific fields how many levels of relationships you search are fully configurable.

Q: Is the tracing functionality present in the existing ArcFM Viewer for ArcFM Server application also part of the new ArcFM Silverlight Viewer released at 9.3.1?
A: Tracing has not made it to the UI yet, but the REST infrastructure is in place.

Q: What kind of data properties can you edit in ArcFM Silverlight Viewer?
A: You don't directly edit data properties in ArcFM Silverlight Viewer. However, ArcFM Silverlight Viewer does honor the ArcFM Properties (e.g. model names) as configured via the ArcFM Properties Manager in ArcCatalog.

Staker

Q: Must you have Designer implemented before you can use Staker?
A: No. While Staker does integrate with Workflow Manager on the enterprise, it is completely separate from Designer. Designer is not required to run Staker.

Express

Q: Does Express use existing feature classes or new "proposed" feature classes when placing facilities?
A: While sketching facilities, all editing occurs with new "proposed" feature classes called Design Feature Classes (DFCs). Even while abandoning or deleting features, the underlying, existing feature class does NOT get edited; rather, it gets 'marked' for abandonment or deletion through the placement of a DFC in its stead.

Q: Is the Design Feature Class (DFC) functionality part of core Designer at 9.3.1?
A: Not yet. It is just present in Express. However, a great deal of consideration is being given to adding DFCs into core Designer and Staker in the near future.

Designer

Q: In addition to front lot construction for subdivisions, is Telvent going to be doing automatic design for overhead and gas?
A: We are still looking into overhead optimization requirements but have not yet discussed gas.

Q: Will the GPS functionality present in Staker (to support the placement of individual stakes) be added to core Designer?
A: It is not something we are considering for the next release.

Configuring ArcFM Mobile: The 9.3.1 Checklists

As promised at this year's Telvent User Group conference, the new and improved ArcFM Solution 9.3.1 Mobile Configuration checklists are now available for downloading. These checklists are designed to guide you through a new installation and configuration of Mobile ArcFM, Mobile Designer, ArcFM Viewer for ArcGIS Engine, Redliner, or Inspector. 

If you are upgrading an old installation, follow the instructions in the "What's New" articles in the ArcFM help instead.

If you are installing at version 9.3 Rev 2, follow the checklists from this earlier post.

***

When your users need to carry geodatabase data into the field with them beyond the reach of high-speed networks, ArcFM Mobile offers a solution. ArcFM Mobile is comprised of two processes:

1. ArcFM Replication, which provides each field machine with a personal geodatabase extracted from the enterprise geodatabase, tailored to include only the feature classes and geographic extents that that machine's users require.  Users can download geodatabase updates manually or schedule them for times when the field machine will be connected to the network. ArcFM Replication can support many different field user interfaces, including standard ArcFM, Designer, ArcFM Viewer for ArcGIS Engine, Redliner, and Inspector.
2. ArcFM Send/Receive, which allows the transmission of sets of redline graphics (and in some cases feature edits) between users. Send/Receive supports standard ArcFM, Designer, Redliner, and Inspector.

As both the geodatabase and one or more servers must be configured to support the chosen interface and processes, determining and implementing the best ArcFM Mobile settings can be challenging. To successfully complete this process, make use of the step-by-step checklists provided below:

    * 9.3.1 Mobile Checklist A: Install software and licenses, do initial geodatabase configuration
    * 9.3.1 Mobile Checklist B: Generate the personal geodatabase(s), configure the servers and one test field machine for ArcFM Replication
    * 9.3.1 Mobile Checklist C: Configure servers and one test field machine for ArcFM Send/Receive
    * 9.3.1 Mobile Checklist D: Configure all remaining field machines

Consult the Mobile Checklist Readme for a diagram showing which configuration components are included in each checklist.

Geodatabase Manager: Automated Version Management at Its Finest

This presentation provides a brief introduction to Geodatabase Manager, a new product at 9.3 Rev2 which allows you to automate the processes of reconciling and posting ArcSDE versions in your geodatabase. It can be set up to reconcile and post versions in conjunction with the Process Framework extensions (Session Manager and Workflow Manager) or it can be used independently of Process Framework. Geodatabase Manager allows utilities with large numbers of versions to maintain healthy data by providing a reconcile service that reconciles versions on an on-going basis. It also allows you to set up a nightly batch post process.

Pre recorded for TUG 2010. Presentation (.mp4 file format at a resolution of 1024x768, best viewed with QuickTime)

Configuring Replication: The Critical Checklist

When your users need to carry geodatabase data into the field with them beyond the reach of high-speed networks, ArcFM Mobile offers a solution. ArcFM Mobile is comprised of two processes:

1. ArcFM Replication, which provides each field machine with a personal geodatabase extracted from the enterprise geodatabase, tailored to include only the feature classes and geographic extents that that machine's users require.  Users can download geodatabase updates manually or schedule them for times when the field machine will be connected to the network. ArcFM Replication can support many different field user interfaces, including standard ArcFM, Designer, ArcFM Viewer for ArcGIS Engine, Redliner, and Inspector.
2. ArcFM Send/Receive, which allows the transmission of sets of redline graphics (and in some cases feature edits) between users. Send/Receive supports standard ArcFM, Designer, Redliner, and Inspector.

As both the geodatabase and one or more servers must be configured to support the chosen interface and processes, determining and implementing the best ArcFM Mobile settings can be challenging. To successfully complete this process, make use of the step-by-step checklists provided below:

• Mobile Checklist A: Install software and licenses, do initial geodatabase configuration
• Mobile Checklist B: Generate the personal geodatabase(s), configure the servers and one test field machine for ArcFM Replication
• Mobile Checklist C: Configure servers and one test field machine for ArcFM Send/Receive
• Mobile Checklist D: Configure all remaining field machines

Consult the Mobile Checklist Readme for a diagram showing which configuration components are included in each checklist.

Pre recorded for TUG 2010. Presentation (.mp4 file format at a resolution of 1024x768, best viewed with QuickTime)

Process Manager: A Real Time Jobs Dashboard

Whether you are running Session Manager in ArcFM or Workflow Manager in Designer, you can benefit from Process Manager. An out of the box executable provided with the core ArcFM Solution install, Process Manager is a standalone application that allows users to monitor the real time status of all jobs across the enterprise. With a simple interface resembling that of Session Manager and Workflow Manager, this application permits a multitude of actions with any given Session or Design, be it examination of job progress, creation and/or reallocation of work, review of historical job details, etc..

Even with this significant range of functionality, Process Manager does not consume an ArcFM Solution license. This key benefit permits use across the organization by a host of supervisors, managers, and executives without concern for exceeding a fixed license allotment.

The ProcessManager.exe resides in the ArcFM Solution install directory under \Program Files\Miner and Miner\ArcFM Solution\Bin

A Tip for Pre-Posting in Designer

For many Designer sites "pre-posting", the process of reconciling and posting a completed design job to the master SDE.DEFAULT database version prior to final construction in the field, is a common practice. Pre-posting can offer many benefits: enterprise wide access for visualizing completed jobs, network tracing across new and existing facilities, layout reference for multistage design jobs with facility dependencies, etc..

Designer sites who currently employ pre-posting may benefit from an advanced configuration setting in the Process Framework titled WMSUsePostWhereClause. This setting automatically directs the Verify Design subtask embedded in the standard Design Post task to intelligently limit deletion of a design's features based on the unique Design ID value of the current design (coupled of course with the feature's specific Work Function value). Limiting this delete behavior as such permits a user to reconcile their job to SDE.DEFAULT over its lifetime without fear of mistakenly deleting facilities during a final post that were never part of their specific job.

An administrator can apply this setting (a value of 1 indicating "on") via the Configuration tab within the Process Framework Administration Tool. Refer to the ProcessFrameworkAdminHelp.chm Help file for more detail on this setting as well as a variety of other advanced configurations options.    

Detailed Job Site Mapping with Designer Map Books

When you need to produce close-up, multiple-page maps showing the path of a feeder, the neighborhood affected by a valve isolation, or any other large area, ArcFM Map Books can divide the large area into smaller cells - sized according to your choices - and provide a consistent look and feel across the map pages. ArcFM Map Book content can be printed, or exported as PDFs or image files.

For Designer users, map books also provide a convenient way to map a job site area, typically defined by a work request polygon feature (shown here in blue).

Before you begin, confirm that your GIS administrator has assigned the MAPGRID class model name to the work request polygon feature class, and the MAPGRIDNAME, MAPSHEETNAME, and MAPSHEETANGLE field model names to the appropriate fields within the feature class.

To create map books for work requests, follow these steps:

1. Open a design belonging to the work request.
2. If the work request polygon has not been sketched yet, sketch it to encompass the entire job site area. 
3. Select the work request polygon.
4. On the Designer toolbar, set the Mode Selector to Designer.
5. On the Designer toolbar, click Open the Design Map Book (the button to the left of the Mode Selector).
6. In the map book tree, right-click the top node (named for your work request and design) and choose New Map Set.  Give the map set a title if desired.
7. On the Maps tab, for Layer chose the name of your work request polygon feature class.
8. Click Selected Set.

Now that you have declared your work request polygon as the building block for this map set, all that's left is to choose the look you want for the map plots.

1. On the Options tab, choose a Stored Display and a Page Template (alternately, you can choose just an ArcFM Map Document). 
2. Set the Scale to your desired value, and check Multiple Pages to allow the map to extend over several pages if needed.
3. Click Apply.

With your appearance settings applied, you can now preview, print, or export the new map book. The book will encompass as many pages as necessary to cover the entire work request polygon.

Because this is a Designer map book (made in Designer mode), it will be deleted automatically when the Work Request reaches the end of its lifecycle. However, if you export and save the map book as a PDF, you can keep that PDF as a permanent record of how the job site area looked at the time the work was done.

ArcFM Solution Validation Rules: Data Integrity OOTB

Data integrity ranks high on the importance list for every utility inputing and maintaining their facilities. To this end, the ArcFM Solution offers a variety of out of the box validation rules that can be applied to a geodatabase with a simple configuration setting. These optional rules are assigned in ArcCatalog via the ArcFM Properties Manager and consist of a collection of object and field level checks applicable to electric, gas, water, and sewer verticals.

For a detailed summary of these rules, please refer to the following document.

ArcFM Solution Validation Rules

Three Tips on Snapping

Snapping is a crucial part of every editor's work as it drives network connectivity and supports cartographic standards. Following are three tips to maximize the usability and usefulness of snapping.

Enable Snap Tips: Enabling this setting displays a dynamic fade out text box in the map display listing the feature class and snap command (e.g. Distribution Main : Midpoint) corresponding to highlighted item on the Targets tab of the ArcFM Attribute Editor. These Snap Tips function as an informative visual guide to editors as they sketch new features. To enable this setting, choose Editor > Options from the Editor toolbar, display the General tab in the Editing Options dialog, and check the box for Show Snap Tips.

Consider Snap To Feature: Using this right-click context menu utility provides on-the-fly access to snap commands (Endpoint, Vertex, Midpoint, and Edge) for any visible feature in the map display, even if that feature does not exist in the administratively configured Snapping Environment dialog. Using Snap To Feature can be particularly helpful in maintaining cartographic standards while sketching by providing a mechanism for precision placement and reference (e.g. snapping Overhead Primary to Pole vertices for perfect in-line wire placement). To use this utility, choose any tool from the Sketch palette on the Editor toolbar, right-click in the map display while hovering over the intended "snap to" feature, and choose Snap To Feature > snap command (Endpoint, Vertex, Midpoint, and Edge) from the context menu.

Increase Sticky Move Tolerance: Establishing a slightly increased value (between 15 - 25 pixels) for this setting safeguards against unintentional geometry shifts when using the Edit tool with multiple, overlapping features in the map display. The higher value means an editor must be more deliberate when attempting to move selected features which will maintain their position until the move exceeds this increased tolerance value (e.g. 20 pixels). Subtle mouse movements will no longer result in unintentional feature geometry shifts. To enable this setting, choose Editor > Options from the Editor toolbar, display the General tab in the Editing Options dialog, and type an increased value for Sticky Move Tolerance.