Telecom Tower Sensor Maintenance Logs

This dataset provides comprehensive logs of IoT sensor maintenance and anomaly events across telecom towers, including detailed asset location, event specifics, technician assignments, downtime tracking, and sustainability impact. It enables proactive field service scheduling, supports network reliability analysis, and facilitates sustainability and compliance reporting for telecom infrastructure managers.

  • last updated 28 Oct 2025
  • by GoMask
The brief that made it

Optimizing field service scheduling and resource allocation

Sample rows

preview · 8 of 84 rows · all 23 columns
log_idstringsensor_typestringsensor_reading_valuefloatmaintenance_typestringtower_idstringtower_location_streetstringtower_location_citystringtower_location_statestringtower_location_postal_codestringtower_location_countrystringsensor_idstringevent_typestringevent_datetimedatetimeevent_statusstringanomaly_codestringanomaly_descriptionstringsensor_reading_unitstringtechnician_idstringtechnician_namestringresolution_notesstringdowntime_minutesintegersustainability_impactstringasset_lifecycle_stagestring
LOG20240601-001temperature34.2cleaningTWR-1001123 Elm StAustinTX78701USASNS-2001maintenance2024-06-01T09:23:00completedblankblankCelsiusTECH-101James HoldenSensor cleaned and recalibrated.13energy_optimizedactive
LOG20240601-002vibration6.8blankTWR-100245 Pine AveDallasTX75201USASNS-2002anomaly2024-06-01T10:12:00completedVIB-ERR-05Excess vibration detected above threshold.mm/sTECH-102Naomi NagataChecked mounting, tightened bolts.20reduced_wearactive
LOG20240601-003humidity45.1blankTWR-1003200 Oak BlvdSan AntonioTX78205USASNS-2003scheduled_inspection2024-06-01T11:05:00pendingblankblank%RHblankblankblank0blankactive
LOG20240601-004power228.5software_updateTWR-100478 Maple DrHoustonTX77002USASNS-2004maintenance2024-06-01T13:40:00in_progressblankblankVoltsTECH-103Alex KamalFirmware update underway.7reduced_energy_consumptionmaintenance_due
LOG20240601-005otherblankblankTWR-1001123 Elm StAustinTX78701USASNS-2005replacement2024-06-01T15:12:00completedblankblankblankTECH-104Amos BurtonSensor replaced with new model.25waste_reductionreplaced
LOG20240601-006temperature56.3blankTWR-100245 Pine AveDallasTX75201USASNS-2006anomaly2024-06-01T16:05:00completedTMP-ERR-03Temperature exceeded safe limit.CelsiusTECH-101James HoldenCooling fan replaced.18energy_optimizedactive
LOG20240601-007humidity38.9blankTWR-1005500 Cedar StFort WorthTX76102USASNS-2007calibration2024-06-01T17:22:00completedblankblank%RHTECH-105Clarissa MaoSensor calibrated per spec.11energy_optimizedactive
LOG20240601-008vibration3.2repairTWR-100612 Birch LnEl PasoTX79901USASNS-2008maintenance2024-06-01T18:35:00completedblankblankmm/sTECH-102Naomi NagataReplaced worn bearing.16reduced_wearactive

What the 84 rows show

from the 84-row sample

Power (sensor type) stands out: mean sensor_reading_value is 213.1, against 32.9 for the rest.

  • 40.0median sensor_reading_value
  • 3event statuses
  • 3asset lifecycle stages
  • 5event types
  • 5sensor reading units
  • 12tower location states
Mean sensor_reading_value by sensor_type64 rows
020040034.0temperat…17 rows5.7vibration14 rows54.0humidity17 rows213.1power16 rows
sensor_reading_value64 rows, in bands of 25
0102020187310004110125250sensor_reading_value →

Median 40.0, from 0.0 to 245.7.

maintenance_type32 rows with a value · 52 left blank
  1. repair10
  2. cleaning8
  3. inspection8
  4. software_update6
23 columns by typefrom the column list below
  • string 20
  • integer 1
  • float 1
  • datetime 1

Columns

23 columns in three groups
blueprint · 23 columns
columntypedescriptionexample
Text 20 columns
log_idstringUnique identifier for each maintenance or anomaly event log entryuniqueLOG20240601-001
tower_idstringUnique identifier for the telecom tower where the sensor is locatedTWR-1001
tower_location_streetstringStreet address of the telecom tower123 Elm St
tower_location_citystringCity where the telecom tower is locatedAustin
tower_location_statestringState or province of the telecom tower location12 statesTX
tower_location_postal_codestringPostal code of the telecom tower location78701
tower_location_countrystringCountry where the telecom tower is locatedUSA
sensor_idstringUnique identifier for the IoT sensorSNS-2001
sensor_typestringType of sensor (e.g., temperature, vibration, humidity, power)temperature · vibration · humidity · power · othertemperature
event_typestringType of event logged (e.g., maintenance, anomaly, scheduled_inspection)5 valuesmaintenance
event_statusstringStatus of the event (e.g., completed, pending, in_progress, cancelled)completed · pending · in_progress · cancelledcompleted
maintenance_typestringType of maintenance performed (e.g., cleaning, repair, software_update, replacement)6 values · optionalcleaning
anomaly_codestringCode representing the anomaly detected (if applicable)optionalVIB-ERR-05
anomaly_descriptionstringDetailed description of the anomaly or issue detectedoptionalHumidity exceeded 95%.
sensor_reading_unitstringUnit of measurement for the sensor reading (e.g., Celsius, Volts, %RH)5 units · optionalCelsius
technician_idstringUnique identifier for the technician assigned to the eventoptionalTECH-101
technician_namestringName of the technician assigned to the eventoptionalJames Holden
resolution_notesstringNotes describing how the event was resolved or handledoptionalCooling fan replaced.
sustainability_impactstringDescription or code of sustainability impact (e.g., reduced energy consumption, waste reduction)optionalenergy_optimized
asset_lifecycle_stagestringLifecycle stage of the sensor asset (e.g., active, end_of_life, replaced)active · end_of_life · replaced · maintenance_due · optionalactive
Numbers 2 columns
sensor_reading_valuefloatSensor reading value at the time of event (if applicable)optional34.2
downtime_minutesintegerTotal downtime in minutes caused by the event (if applicable)0 or more · optional13
Dates and times 1 column
event_datetimedatetimeDate and time when the event occurred or was logged2024-06-01T09:23:00

Use it for

  • median sensor …40.064 rowsmean sensor reading v…34.0temp…5.7vibr…54.0humi…213.1power

    A telecommunications dashboard

    Sensor_reading_value by sensor_type and a breakdown of maintenance_type. Excel, Power BI or Tableau.

  • Why do the 16 power rows have a mean sensor_reading_value of 213.1?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable logs with tower_id, tower_location_street and tower_location_city to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 23 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset84 rows23 columns
Yours1,000 rows23 columnstower_location_street: UK only

blueprint · telecom-tower-sensor-maintenance-logs

Behind this dataset

Same schema. As many rows as you need.

These 84 rows came out of a blueprint — 23 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each row records a sensor maintenance event or anomaly detected.
  • Include device ID, tower location, event timestamp, event type (maintenance/anomaly), and resolution status.
  • Flag overdue maintenance events if resolution time exceeds the defined SLA.
  • Sensors reporting anomalies more than twice in 30 days are marked for priority review.
  • Maintenance logs must link to technician ID for accountability.
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
telecom-tower-sensor-maintenance-logs

What should your data show?

Preview 20 rows free
No signup. No card.