A municipality managing 4,000 street lights with a spreadsheet and a fault reporting hotline is always reacting. A fault is reported, a crew is dispatched, a lamp is replaced. What doesn't happen is any systematic picture of which areas have the highest fault frequency, which lamp types are failing disproportionately, which circuits have chronic issues, or whether the nighttime fault rate in a given district is rising. Without a georeferenced inventory with operational status records, the maintenance program is entirely reactive and the capital replacement planning is based on budget cycles rather than actual asset condition.
Daytime vs. Nighttime Status
Estado de dia and Estado de noche with their respective date fields — Fecha de dia and Fecha de noche — are the critical split in this template. A luminaire that passes a daytime inspection (physical condition, support integrity, electrical continuity check) but fails at night (lamp doesn't ignite, photocell fault, driver failure) is a different maintenance item than one with a physical damage issue visible in daylight. The two status fields with separate inspection timestamps mean a technician doing a nighttime drive-through inspection can log status independently of the daytime inspection record, building a dual-mode picture of each unit.
Potencia (wattage) and Medida (electrical measurement) are the specification fields that drive both energy consumption calculations and replacement procurement. A district with mixed 70W SON-T and 150W SON-T on the same circuit has a different load profile than one fully standardized on 100W LED equivalents. The wattage record per unit is what enables actual consumption calculation rather than estimated averages, and it's the basis for LED retrofit projects that need to confirm the existing load before specifying replacement units.
The Location Record
Coords with Calle (street), Localidad (locality), and Municipio (municipality) creates a three-level address hierarchy plus a GPS anchor. In rural or peri-urban areas where street naming is inconsistent or incomplete, coordinates are the primary location identifier. In urban areas, the street and locality fields provide the navigable address while coordinates provide the verifiable location. A luminaire database without coordinates produces maps with address-level precision; one with coordinates produces maps with metre-level precision.
Tipo Apoyo (support type) — concrete column, metal pole, wall bracket, catenary suspension — is the field that feeds into the structural inspection program. Different support types have different inspection intervals and different failure modes under wind loading, corrosion, and vehicle impact. Filtering the inventory by support type gives the maintenance team the right checklist for each inspection type rather than applying a single protocol across different structures.
Codigo_lum is the unique identifier that ties the Memento record to the GIS layer, the work order system, and the fault report. When a fault call references a lamp on Calle Major near the junction with Avenida Industrial, the crew that arrives looks for the Codigo_lum stencilled on the column, logs it, and the maintenance event is recorded against the correct asset record rather than estimated from location description.
CT identifies the control circuit — the feeder that powers that luminaire alongside all the others on the same branch. When a circuit trips and twenty lights go out simultaneously, the CT field is what produces the affected lamp list for restoration, and it's what identifies the common circuit for fault diagnosis when multiple luminaires on the same branch start failing within a short period.
Nombre tecnico closes each record with technician identity — the person who inspected or serviced this specific unit on this date. That's the accountability record for a programme where multiple crews work independently across a large geographic area.