Home / Case Studies
While all ArcGIS/ArcFM implementations have their unique aspects, many design elements and implementation tasks are similar from project to project. Here we’ve tried to assemble a set of data-focused project experiences that may be common to a task you’re trying to accomplish or requirement you hope to meet. Hopefully you’ll find some nugget from among these cases that proves helpful. Finally, if there’s a topic not listed you’d like to see discussed, please let us know.
We created a “Device Connectivity” table from an ArcFM™ Feeder Manager-managed electric distribution network to support a single, isolated business function. In the course of a year’s time we found and implemented multiple applications all taking advantage of the same table. Could have been a little serendipitous, but in our case the initial investment proved quite worthwhile.
Sometimes quality assurance processing can be, shall we say, um… sluggish. We recently had an experience where ArcFM™/Designer QA performance was quite so. This article describes how we diagnosed performance issues and ultimately improved things. A lot.
In a previous post we discussed methods for providing multiple geometries for a given feature. The options described included ArcSchematics, cartographic representations and use of related feature classes. In this post we take on a similar but different topic of creating an additional geometry definition in an existing feature class that is managed entirely by a custom application.
We've done a lot of serious case studies in the past year. This one's for a little fun. Enjoy!
Feeder definitions are often extracted from an electric GIS database and loaded into other business-critical applications like OMS, DMS and system planning. Typically it’s impractical to export *all* feeders all the time. Detecting those that have changed - and thus "dirty" - becomes an important part of the process.
The configurability of the ArcFM Solution many times lets us match functionality to our data model - and not have to adjust the data model to achieve needed functionality. This post provides an example for a water distribution system
The register as versioned "Move to Base" option that is. This post takes a deep dive into whether it might make sense to take advantage of it.
In a previous post on GIS data quality required to support an ADMS implementation we posed the question "How Good Is Good Enough?" This post digs in to some more of the detail needed to answer that question.
Management of proposed equipment may seem straightforward but can complicated quickly. However, just because its complicated doesn't mean its not a requirement. This post outlines some considerations.
As ADMS tecnology increases in popularity so must GIS data quality improve to support it. This is the first post in a series where we explore GIS-ADMS data quality needs.
Unlike other electric distribution data models, the ArcGIS Electric model provides three fields for normal position in a switch/protective device. This post explores a little of the background to why.
Its rare, but ArcFM AutoUpdaters can stop working. However, they don't stop on their own, there is always an underlying reason. This post can help with the diagnosis and resolution.
This post explores the way distribution transformers are represented in the ArcGIS/ArcFM electric model, and particularly the modeling of connectivity to support tracing.
ArcFM's Feeder Manager expects a "head" from which downstream equipment is energized. Turns out this can mean different things to different implementations. This post explores strategies we've seen.
You may (or may not) have noticed that an extra vertex is added on line crossing when you build a geometric network. This post explores the details.
While ArcGIS Archiving can track all edits performed in your Geodatabase at a system level. But Archiving might not be for you. This post discusses some options.
This post explores modeling utility infrastructure components within ArcGIS/ArcFM. Here we'll talk about Overhead Neutral Wire.
The standard electric models are a little fuzzy on the topic. This post explores three options we've implemented in past projects.
Some business cases call for multiple depictions of mapped features based on the anticipated use of the data. Not moving things around like white space management, but using multiple geometries. We explore the available approaches.
This post is the first in a series in which we’ll explore specifics of modeling utility infrastructure components within ArcGIS/ArcFM. To start we’ll address electric distribution conductors.
In a previous post we addressed several important capabilities offeredd by ArcGIS Archiving. But the subject is too big for a single post.
Given that there always will be users creating map content in AutoCAD and Microstation it makes sense to have a smart way to incorporate that content into your Geodatabase.
ArcGIS Archiving provides a product-based solution for answering questions like: When did this (gas main, service, conductor) get deleted? This post provides a preliminary deep-dive.
When validating your utility geometric network connectivity one of the hardest things to do is figuring out what exactly is connected to what. Rendering junction "valence" can help.
This case study examines a potentially hazardous condition for which we can identify candidate locations.
Phase designation and phase configuration are similar but different properties. Here's a way to combine them into one field.
ArcFM Valve Isolation tracing provides very valuable functionality. If you don't have all the data it expects, here's a way to simulate it.
Migrating AutoCAD or Microstation data into ArcFM has been done many times, and can be straightforward. But usually the best results come with thoughtful preparation.
In most cases you would expect an ArcFM CP trace include all connected CP features. This entry describes a case where you may not.
There are pros and cons to setting default values on migration into ArcFM. Just make a conscious decision about your approach.
In most cases if a company has equipment located inside a “container” – like an electric or gas station - a polygon container already exists. This post discusses an approach when you don't.
Record counts alone are usually not a good predictor of effort to migrate from one electronic source to another.
The foundation of a ArcFM Fiber Manager implementation is the Fiber Manager "flexible data model."
ArcFM uses trace weight fields to inform its tracing functions about attribute values used to decide whether to go or stop. Here we show a tool that interprets gas trace weights, similar to the ArcFM Electric Trace Weight Inspector.
Dealing with anomalies is an important aspect of ensuring a high quality data migration.
ArcFM Feeder Manager typically considers a "source" to be a substation circuit breaker. In some cases one might also consider as sources step-down transformers (either inside or outside of the substation).
Transforming equipment from "Internal Worlds" is often a requirement when migrating data from Smallworld GIS into an ArcFM Geodatabase. This Case Study reviews some of the critical steps.