Tracking multiple repairs with cost.

Question

Hello all, I'm not sure if this is the correct community to ask this question in but here I go. I am currently mapping the irrigation system for my company and have been trying to find a way to input multiple repairs and their cost so I can go back and do an analysis of cost/ how many repairs/ what is being replaced. I cannot figure out a way in the forms section to make it to where you can input multiple repairs on different dates to the same thing (ex. rotor, valve, line). Is there a way to do this so that I can log all of my repairs in the field and then later be able to analyze the data that I input.

Something similar to clicking on a rotor and putting (repair date- 6/24/26- rotor replaced, cost $20) and then having the ability to add an another repair in the future.

OsvaldoDiaz · Answer

Hola! Si, esta es la comunidad ideal para su consulta.

Para estructurar reparaciones y costos asociados a un activo (como una tubería o válvula) sin generar redundancia geométrica , te sugiero evitar a toda costa el uso de tablas planas en un solo feature. Lo técnicamente correcto es implementar Clases de Relación (Relationship Classes) de tipo uno -a-muchos (1:M) entre su capa espacial de red y una tabla relacional de inspecciones u órdenes de trabajo(por ejemplo,Water Line,Maitenence Inspection o una tabla de historial de reparaciones).

rkrisher · Answer

Another way you can do this is to set up a Survey123 form to capture the information that includes a unique ID for the asset. You can then use a dashboard (or arcade expression, python script, join layer, etc) to bring the two datasets together for reporting purposes.

I just got done writing a series of microblogs outlining this technique on LinkedIn, and I'm in the process of rewriting the series into a series of community posts. DM me if you want the link to the original article(s) in the meantime.

joyoung_kerrvilletx · Answer

The way to do that is using a related table to track the repairs using a one to many relationship. Unfortunately with the way ArcGIS Online and ArcGIS Enterprise currently work, you will have to republish your layers after creating the relationships between the asset layers and the repair tables in ArcGIS Pro. Here is Esri's documentation on relationship classes: https://doc.esri.com/en/arcgis-pro/latest/tool-reference/data-management/create-relationship-class.html?tabs=dialog

I would recommend one repair table for each asset layer you have, instead of trying to relate one repair table to many asset layers. For example, a sprinkler point layer should have one related table and a valve point layer should have a different related table.

ArcGIS Field Maps has much better support for related tables now. Select an asset on the map and in the popup there should be a button to add a related record to the asset. Also, the ArcGIS Solutions Irrigation System Data Management solution already has a related inspection table for its assets that you can add a repair cost field to.