FME is used at PNM for a wide variety of purposes including: 1. Buffering underground utility lines and formatting outage data for maps 2. Processing new service data and calculating distribution infrastructure metrics 3. Converting and extracting GIS data for use in other systems like CAD and for reporting, auditing, and analyzing assets, outages and joint use infrastructure.

1. FME @ PNM:
A Cornucopia
of Uses
Aaron Allen
Rene Carrillo

2. Distribution Service Areas for PNM & TNMP

3. FRAMME to ESRI FME Script

4. FME Scripts Used Regularly
1. NM One Call (monthly) – Buffers primary and secondary underground
distribution lines, which are used by NM One Call to determine if PNM needs to
be included in a locate request.
2. New service delivery (daily) – Uses GIS data to error check gross receipts
information for new services.
3. PNM web map metrics (quarterly) – Tabulates user hits for various PNM web
maps.
4. Create THOR files from ArcGIS Online data (daily) – Converts ArcGIS Online
data for street light outages into THOR files for use with BCLAMPS.
5. Get PoleID and set CloseDate fields in street light data (hourly) – Automatically
finds PoleID and sets CloseDate for ArcGIS Online street light data.
6. Calculate TwoWeeksAgo field in street light data (daily) – Sets the date for two
weeks past to enable hiding of older closed street light records from the map.
7. Back up ArcGIS Online street light data (daily) – Generates back up of street
light data in case of disaster, data corruption, etc.
8. Provide data for PNM outage map (every 10 minutes) – Converts tabular data
for map use and formats fields for presentation on PNM outage map.
9. Calculate primary distribution miles (annually) – Calculates miles of overhead
and underground primary distribution for annual reports.
10. Provide 3D points for substation changes (periodically) – Clips and converts
DEM raster data into XYZ points for use with PLSCADD.
11. Extract ArcFM data to CAD for joint use (as needed) – Provides joint use
attachers stripped down CAD data for joint use applications.
12. Extract ArcFM data to CAD for PNM landbase (as needed) – CAD extracts are
compared with subdivision landbase CAD data provided by surveyors to better
place new landbase data in ArcFM database.
13. Blue book (weekly) – Tracks changes in ArcFM data to update blue book pages.
14. Hyperlink checker (periodically) – Compares Work Order IDs and several
Hyperlink fields in ArcFM to identify unpopulated hyperlink records.
15. Cogen report (monthly) – Creates a tabular report for both Renewable
Resources and Distribution Planning that, for each cogen, finds the transformer
and feeder it is attached to.
16. Account Plant audit (annually; as requested) – Provides detailed asset
information about many PNM and TNMP GIS layers to Account Plant for annual
IRS audit.
17. Joint use report by customer (bi-annually) – Summarizes all joint use customers
and their attachments on the PNM system for T&D Asset Management.
18. Franchise fee report (bi-annually) – Identifies franchise fees on joint use poles
and also determines whether they are inside or outside city limits.
19. TNMP joint use audit (monthly) - Extracts TNMP data based on TNMP regions
for contractors performing the joint use audit.
20. Synergee landbase extract (monthly) - Extracts and tiles landbase data from
ArcFM, then converts it to an AutoCAD dwg file for use as a backdrop with the
Synergee application.
21. TNMP Millsoft extract (monthly) – Extracts ArcFM data into TNMP regions for
use with the Millsoft application.
22. ArcFM Mobile sync report (weekly) – Generates and emails a report of all the
ArcFM Mobile laptops that have synced with the database in the past 7, 14, and
30 days.
23. NM/TX bird outages (daily) - Generates points features for all bird related
outages for the Environmental Department.
24. Clearion sync checker (daily) – Checks the status of service orders between
Oracle and SqlServer and reports if there are any discrepancies.
25. Deleted pole checker (daily) – Checks for support structures that have been
accidently deleted from ArcFM by looking at geographically related features that
are no longer near a pole.

25. DWG Styler

36. Main Point
If you delete a layer on ESRI’s
AGOL, it’s gone forever! Creating
a new layer with the same name
is not the same layer. It has a
different ID.
Truncating your AGOL data with
FME lets you retain the empty
layer with its schema. You can
then load data with FME or add
new data directly in AGOL.

37. Thank you!
Questions?