Fast-Track Electric Utility Inventory- A Case Study

Training
Training was one of the most difficult of many difficult aspects of this large project for us. There were so many new concepts and specifics to learn to do this job accurately and effectively. A few of the concepts we needed to teach were:

Electrical Distribution concepts
Electrical Distribution equipment, devices, wires etc.
GPS receivers, how they work and don’t work
Personal computers and DOS (many didn’t even know the word “DOS” when we started)
GeoLink GPS-Mapping software
ArcView GIS
Internet browsers and e-mail
How to read Fusing and Circuit maps and diagrams
Unique codes, syntax, and attribute values such as AAAC, CW, Mid-Span Taps, Dual Bushing, Knife-blade etc.

We began the initial three week training program by describing Allegheny Power’s goal of this project and gaining an understanding of why they are conducting it. We described the final connectivity model that Allegheny would own as a result, and how that would be used to study the electrical flow, perform engineering analysis, and allow for more advanced design and outage management processes. We taught how the basis for this is a digital connectivity model, and that the basis for that is Phasing and Backspan (the serving pole ID#) information. We showed a short example of a field collection simulation then translated it into a GIS map to show our collectors how their field work will translate directly into an intelligent map (“a connectivity model”).

The next training topic was the Global Positioning System and how we receive and utilize the data from it. I think we spent too much time here and got too deep into the frequencies, carrier phases, and signal processing than we really needed. It also overwhelmed many of our collectors and they had trouble concentrating on the more meaningful topics that followed. In subsequent training sessions, a lot of technical details of the Global Positioning System were eliminated. The GPS field collection software was the next training topic. It was useful to run simulations of the software demonstrating the pole collection that we’d be soon performing in the field. We were able to train each collector how to start the software (DOS commands), how to name files, and how to collect and correctly attribute each of the features we would need to map (Poles, Pad-Mounts, Secondary Poles, Transformers, Fuses etc.). Each collector received plenty of hands-on practice in-office on a wide screen monitor to gain familiarity with the software and the collection methodology. The simulated files were then translated into GIS maps that were then reviewed for connectivity and attribute accuracy. This was one of the most useful parts of our training program and prepared our new collectors for the field practice to follow.

The field practice involved everyone mapping a circuit from a nearby substation. A circuit was selected which had a representative mix of features on it, and was in a somewhat rural area (to allow 20 people to safely work and walk around the poles). This was the first opportunity we had to identify the phasing of the conductors, determine the size and type of conductors, and identifi the devices on the poles. We spent nearly a week on the practice circuit, working slowly in the cold and snow of November, to give each collector experience on each aspect of the job. Again, the aspects of the job were to: 1) identify the characteristics of a pole, 2) record the information accurately, and 3) determine which pole to map next. The task began to seem much easier when viewed in these simplistic terms.

One of our most beneficial training ideas was to pair an experienced former Allegheny staffer, with a computer or GPS literate employee. Often, we had a 45-60 year old former lineman or engineer who knew everything about the electrical system and nothing at all about personal computers, DOS or GIS, working alongside a 20-25 year old computer literate recent Geography or Engineering graduate. This cross-training proved invaluable, and we continued it as a model for new hires throughout the project.

The data collected during our practice sessions was translated and reviewed as a group. In retrospect, we should have spent a lot more time on this aspect. It would have been useful to demonstrate (repeatedly) how such things as a single bad attribute value (like Phasing) can cause the connectivity model to fail, or show what an erroneous GPS coordinate or Backspan could do to the map.