Smart Park Device Uptime Log

This dataset provides detailed logs of IoT device uptime, usage events, downtime causes, and maintenance interventions across public parks, enabling city managers and urban planners to optimize maintenance schedules, reduce device failures, and enhance visitor experience. Each entry includes device location, operational status, event counts, and intervention details for comprehensive operational oversight.

  • last updated 30 Nov 2025
  • by GoMask
The brief that made it

Optimizing park device maintenance schedules

Sample rows

preview · 8 of 121 rows · all 18 columns
log_idstringdevice_typestringusage_event_countintegeroperator_idstringdevice_idstringpark_idstringpark_namestringlocation_latitudefloatlocation_longitudefloatstatusstringstatus_timestampdatetimeuptime_duration_minutesintegerlast_downtime_startdatetimelast_downtime_enddatetimedowntime_causestringmaintenance_interventionstringmaintenance_timestampdatetimenotesstring
A8X3-1KFsensor89TECH-01SEN-4321PARK-01Central Green40.785091-73.968285online2024-06-01T09:03:21Z23452024-05-27T13:11:19Z2024-05-27T15:18:44Znetwork-issuereset2024-05-27T15:30:00ZDevice recovered from network outage after technician reset.
B1Q8-7HPcamera0TECH-02CAM-1145PARK-02Willow Creek Park34.052235-118.243683maintenance2024-06-02T12:22:16Z02024-06-02T08:00:00Z2024-06-02T08:30:00Zscheduled-maintenancefirmware-update2024-06-02T11:00:00ZRoutine firmware update and calibration completed.
D7L2-3NVlighting3200blankLGT-6678PARK-03Liberty Park41.878113-87.629799online2024-06-03T18:41:19Z1200422024-05-30T17:00:00Z2024-05-30T18:10:00Zscheduled-maintenancenoneblankLighting system has had remarkable uptime since last update.
E5M9-2JFenvironmental-monitorblankTECH-03ENV-8453PARK-01Central Green40.785091-73.968285error2024-06-04T07:09:50Zblank2024-06-04T06:30:00Zblanksoftware-errorreset2024-06-04T07:00:00ZMonitor entered error state due to software malfunction. Reset performed.
F6S1-4QGaccess-control0blankACC-2001PARK-04Oakridge Commons37.774929-122.419416offline2024-06-05T11:15:37Z02024-06-05T07:30:00Zblanknetwork-issueresetblankAccess control offline due to network connectivity loss, awaiting technician.
G2K7-5NCsensor70TECH-04SEN-0432PARK-05Riverfront Plaza35.227087-80.843127online2024-06-06T08:45:12Z15402024-05-31T14:10:00Z2024-05-31T15:05:00Zhardware-failurerepair2024-05-31T15:30:00ZSensor repaired after hardware issue. Functionality restored.
H4B9-6PQcamera0TECH-05CAM-2789PARK-06Heritage Fields39.739236-104.990251maintenance2024-06-07T16:55:32Z02024-06-07T12:40:00Z2024-06-07T13:00:00Zscheduled-maintenanceinspection2024-06-07T14:00:00ZCamera scheduled for lens cleaning and system inspection.
I8U2-7WRlighting9520blankLGT-3221PARK-02Willow Creek Park34.052235-118.243683online2024-06-08T22:17:11Z2012312024-06-04T21:00:00Z2024-06-04T22:10:00Zpower-outagenoneblankLighting online; last downtime caused by brief power outage.

What the 121 rows show

from the 121-row sample

Lighting (device type) stands out: mean usage_event_count is 5,547, against 39.6 for the rest.

  • 49median usage_event_count
  • 4statuses
  • 6downtime causes
  • 6maintenance interventions
  • 1,540median uptime_duration_minutes
Mean usage_event_count by device_type97 rows
04,0008,000110.2sensor25 rows0.0camera25 rows5,547lighting24 rows5.8access-c…23 rows
usage_event_count97 rows, in bands of 1,000
040807414331133405,00010kusage_event_count →

Median 49, from 0 to 9,999.

operator_id81 rows with a value · 40 left blank
  1. TECH-103
  2. TECH-113
  3. TECH-123
  4. TECH-133
  5. TECH-143
  6. TECH-153
  7. TECH-163
  8. TECH-173
  9. TECH-183
  10. TECH-193
18 columns by typefrom the column list below
  • string 10
  • integer 2
  • float 2
  • datetime 4

Columns

18 columns in three groups
blueprint · 18 columns
columntypedescriptionexample
Text 10 columns
log_idstringUnique identifier for each uptime log entryuniqueA8X3-1KF
device_idstringUnique identifier for the IoT deviceSEN-4321
device_typestringType of IoT device (e.g., sensor, camera, lighting)6 valuessensor
park_idstringUnique identifier for the park where the device is locatedPARK-01
park_namestringName of the public parkCentral Green
statusstringCurrent operational status of the deviceonline · offline · maintenance · erroronline
downtime_causestringReason for the most recent downtime (e.g., hardware failure, network issue, scheduled maintenance)7 values · optionalnetwork-issue
maintenance_interventionstringType of maintenance performed during the last intervention7 values · optionalreset
operator_idstringIdentifier for the technician or operator who performed maintenanceoptionalTECH-01
notesstringAdditional notes or comments related to the log entryoptionalDevice recovered from net…
Numbers 4 columns
location_latitudefloatLatitude coordinate of the device location in the park-90 to 9040.785091
location_longitudefloatLongitude coordinate of the device location in the park-180 to 180-73.968285
uptime_duration_minutesintegerTotal minutes the device has been online since last downtime0 or more · optional2345
usage_event_countintegerNumber of usage events recorded since last status change0 or more · optional89
Dates and times 4 columns
status_timestampdatetimeTimestamp when the current status was recorded2024-06-01T09:03:21Z
last_downtime_startdatetimeTimestamp when the most recent downtime period beganoptional2024-05-27T13:11:19Z
last_downtime_enddatetimeTimestamp when the most recent downtime period endedoptional2024-05-27T15:18:44Z
maintenance_timestampdatetimeTimestamp when the last maintenance intervention occurredoptional2024-05-27T15:30:00Z

Use it for

  • median usage e…4997 rowsmean usage event coun…110.2sens…0.0came…5,547ligh…5.8acce…

    A government dashboard

    Usage_event_count by device_type and a breakdown of operator_id. Excel, Power BI or Tableau.

  • Why do the 24 lighting rows have a mean usage_event_count of 5,547?

    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 device_id, device_type and park_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 18 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 dataset121 rows18 columns
Yours1,000 rows18 columnslocation_latitude: UK only

blueprint · smart-park-device-uptime-log

Behind this dataset

Same schema. As many rows as you need.

These 121 rows came out of a blueprint — 18 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 device entry must include type, location, and unique ID.
  • Downtime events require timestamp, duration, and cause classification.
  • Maintenance interventions logged only if downtime exceeds 30 minutes.
  • Usage events recorded hourly per device if active.
  • Devices flagged for replacement after more than three critical faults in 30 days.
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
smart-park-device-uptime-log

What should your data show?

Preview 20 rows free
No signup. No card.