When the Terrain Disagrees with the Database
A field technician arrives at the address tied to NIS 40521 and finds a transformation center that does not match the CT identifier in MDSIG. The database says the supply point belongs to CT-A4-221. The transformer on the pole 30 metres down the street says CT-A4-189. The lot number on the finca matches, but the CT attribution is wrong.
This discrepancy can sit unresolved for months if there is no mechanism to capture it at the point of discovery. The technician finishes the job and moves on. The MDSIG record stays incorrect. The next technician working from the same database assumes the same wrong CT and routes the wrong crew to the wrong point of the network.
The VSum audit record exists to surface these mismatches in real time, with GPS coordinates and a classified error type, so the database correction backlog has a structured input queue rather than verbal reports filtered through office staff.
The Comparison Fields That Reveal the Discrepancy
LOTE MDSIG and LOTE TERRENO hold the lot number as it appears in the geographic information system and the lot number as verified on the ground. These should be the same. When they are not — when the GIS shows a cadastral lot number that does not match the physical lot markers or the municipal address plate on the fence — the discrepancy is logged here, with both values, not overwritten. The historical difference matters for the database correction team.
CT MDSIG and CT Terreno are the transformation center identifiers that carry the same before/after structure. A CT error is the most consequential classification in the Tipo Error field: misattributing a supply point to the wrong CT means network outage events trace to the wrong segment, load calculations on that CT are skewed, and fault isolation during a failure event sends maintenance to the wrong location.
The three error types — CT Erróneo, Punteo Erróneo, and Error en Dirección — cover the three failure modes. CT Erróneo is the supply point attributed to the wrong transformation center. Punteo Erróneo is a geolocation error: the GIS point does not correspond to the physical address. Error en Dirección is a street or door number mismatch in the database that causes the technician to be routed to the wrong property. All three are distinct correction workflows in the back-office GIS team.
The Estado Field as the Verification Queue
Estado — Tiene Error, No Tiene Error, No Verificado — is the triage filter. On a batch of 200 VSum records, filtering by Estado: No Verificado shows the queue. Filtering by Estado: Tiene Error shows the correction backlog. The GIS team processes corrections in the order the field data comes in. A record that sits on No Verificado for three weeks has not been reviewed; a record on Tiene Error that has not been assigned for correction is a discrepancy that is accumulating operational risk.
The Solicitud field carries the request reference — the work order or ticket number that initiated the field visit. This ties the VSum record back to the job management system so the resolution can be tracked end-to-end: which field visit surfaced the error, when the correction was submitted, and whether the MDSIG record has been updated.
The GPS Coords field is the ground-truth anchor. When the physical address on file is ambiguous or the street numbering in the municipality is not sequential, the GPS coordinates locate the meter point unambiguously. A point with a verified coordinate that disagrees with the MDSIG polygon boundary is a geolocation correction the mapping team can act on without a second field visit.